@ives_xxz/packages 1.0.0

package/Quick Finder/typings/vue.d.ts

@@ -0,0 +1 @@
+declare var Vue: any;

package/README.md

@@ -0,0 +1,93 @@
+# packages
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin http://47.243.247.195:8099/crazy_client/packages.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+- [ ] [Set up project integrations](http://47.243.247.195:8099/crazy_client/packages/-/settings/integrations)
+
+## Collaborate with your team
+
+- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
+- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

package/package.json

@@ -0,0 +1,12 @@
+{
+  "name": "@ives_xxz/packages",
+  "version": "1.0.0",
+  "description": "cocoscreator 2.x plugins",
+  "main": "index.js",
+  "scripts": {
+  },
+  "keywords": ["123456"],
+  "author": "ives",
+  "license": "ISC"
+  
+}

package/unpack plist/main.js

@@ -0,0 +1,253 @@
+/****************************************************************************
+Copyright (c) 2016-2017 steven
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+****************************************************************************/
+
+'use strict';
+const Fs = require('fire-fs');
+const Path = require('fire-path');
+const Async = require('async');
+const Del = require('del');
+
+let sharpPath;
+if (Editor.dev) {
+    sharpPath = 'sharp';
+} else {
+    sharpPath = Editor.url('unpack://utils/sharp');
+}
+const Sharp = require(sharpPath);
+
+const dontSelectCorrectAssetMsg = {
+    type: 'warning',
+    buttons: ['OK'],
+    titile: 'Unpack Texture Packer Atlas',
+    message: '请选择一个plist文件!',
+    defaultId: 0,
+    noLink: true
+};
+
+let isSelectAsset = false;
+function hook_function(param1, param2, param3) {
+    let add = function () {
+        return param3(arguments), new param1(...arguments);
+    };
+    let obj = Object['getOwnPropertyNames'](param1);
+
+    for (let i of obj) {
+        const object = Object['getOwnPropertyDescriptor'](param1, i);
+
+        if (object['writable']) {
+            add[i] = param1[i];
+        }
+    }
+    Editor.log('结束');
+    return (add['prototype'] = param1['prototype']), add;
+}
+
+module.exports = {
+    load() {
+        //Editor.log('start');
+        let ipc_listen_o = new Editor.IpcListener();
+        ipc_listen_o.on('selection:context', function () {
+            //Editor.log(arguments, 'arguments');
+            if (arguments[1] == 'asset') {
+                isSelectAsset = true;
+                //// curSelectAsset = arguments[2] ? Editor.assetdb.uuidToFspath(arguments[2]) : null;
+            } else {
+                isSelectAsset = false;
+            }
+        });
+
+        if (Editor['__hookedEditorMenu__'] != undefined) {
+            return;
+        }
+
+        Editor['__hookedEditorMenu__'] = true;
+
+
+        var self = this;
+        Editor.Menu = hook_function(Editor.Menu, {}, function (v_as) {
+            if (!isSelectAsset) {
+                return;
+            }
+            let template = [
+                {
+                    type: 'separator',
+                },
+
+                {
+                    label: 'plist拆分',
+                    click: () => {
+                        //Editor.Ipc.sendToPanel('unpack-textureatlas.unpack', null);
+                        self.chaiPlist();
+                    },
+                },
+                {
+                    type: 'separator',
+                },
+
+            ];
+            console.log('v_as', v_as);
+            v_as[0].push(...template);
+        });
+    },
+
+
+    unload() {
+        // execute when package unloaded
+    },
+
+    chaiPlist() {
+        Editor.Metrics.trackEvent({
+            category: 'Packages',
+            label: 'unpack-textureatlas',
+            action: 'Open By Menu'
+        }, null);
+
+        let currentSelection = Editor.Selection.curSelection('asset');
+        if (currentSelection.length > 0) {
+            let selectionUUid = currentSelection[0];
+            let selectionMeta = Editor.assetdb.loadMetaByUuid(selectionUUid);
+            let selectionUrl = Editor.assetdb.uuidToUrl(selectionUUid);
+            let assetInfo = Editor.assetdb.assetInfoByUuid(selectionUUid);
+            const textureAtlasPath = Editor.assetdb.uuidToFspath(selectionMeta.rawTextureUuid);
+
+
+            if (!textureAtlasPath) {
+                Editor.Dialog.messageBox(dontSelectCorrectAssetMsg);
+                return;
+            }
+            let textureAtlasSubMetas = selectionMeta.getSubMetas();
+
+            if (assetInfo.type === 'sprite-atlas' &&
+                selectionMeta.type === 'Texture Packer' &&
+                textureAtlasSubMetas) {
+                // In Creator Editor version 2.2.2,use Editor.Project.path 
+                let extractedImageSaveFolder = Path.join(Editor.Project.path, 'temp', Path.basenameNoExt(textureAtlasPath) + '_unpack');
+                Fs.mkdirsSync(extractedImageSaveFolder);
+
+                let spriteFrameNames = Object.keys(textureAtlasSubMetas);
+                Async.forEach(spriteFrameNames, function (spriteFrameName, next) {
+                    let spriteFrameObj = textureAtlasSubMetas[spriteFrameName];
+                    let isRotated = spriteFrameObj.rotated;
+                    let originalSize = cc.size(spriteFrameObj.rawWidth, spriteFrameObj.rawHeight);
+                    let rect = cc.rect(spriteFrameObj.trimX, spriteFrameObj.trimY, spriteFrameObj.width, spriteFrameObj.height);
+                    let offset = cc.v2(spriteFrameObj.offsetX, spriteFrameObj.offsetY);
+                    let trimmedLeft = Math.ceil(offset.x + (originalSize.width - rect.width) / 2);
+                    if (trimmedLeft < 0) trimmedLeft = 0;
+                    let trimmedRight = Math.ceil((originalSize.width - rect.width) / 2 - offset.x);
+                    if (trimmedRight < 0) trimmedRight = 0;
+                    let trimmedTop = Math.ceil((originalSize.height - rect.height) / 2 - offset.y);
+                    if (trimmedTop < 0) trimmedTop = 0;
+                    let trimmedBottom = Math.ceil(offset.y + (originalSize.height - rect.height) / 2);
+                    if (trimmedBottom < 0) trimmedBottom = 0;
+
+                    let sharpCallback = (err) => {
+                        if (err) {
+                            Editor.error('Generating ' + spriteFrameName + ' error occurs, details:' + err);
+                        }
+
+                        Editor.log(spriteFrameName + ' is generated successfully!');
+                        next();
+                    };
+
+
+                    let bok = spriteFrameName.endsWith('.png')
+                    if (!bok && !spriteFrameName.endsWith('jpg')) {
+                        spriteFrameName = spriteFrameName + '.png'
+                    }
+
+                    let extractedSmallPngSavePath = Path.join(extractedImageSaveFolder, spriteFrameName);
+
+
+                    if (isRotated) {
+
+                        Sharp(textureAtlasPath).extract({
+                            left: rect.x,
+                            top: rect.y,
+                            width: rect.height,
+                            height: rect.width
+                        })
+                            .extend({
+                                top: trimmedTop,
+                                bottom: trimmedBottom,
+                                left: trimmedLeft,
+                                right: trimmedRight,
+                                background: {
+                                    r: 0,
+                                    g: 0,
+                                    b: 0,
+                                    alpha: 0
+                                }
+                            })
+                            .rotate(270)
+                            .toFile(extractedSmallPngSavePath, sharpCallback);
+
+                    } else {
+                        Sharp(textureAtlasPath).extract({
+                            left: rect.x,
+                            top: rect.y,
+                            width: rect.width,
+                            height: rect.height
+                        })
+                            .extend({
+                                top: trimmedTop,
+                                bottom: trimmedBottom,
+                                left: trimmedLeft,
+                                right: trimmedRight,
+                                background: {
+                                    r: 0,
+                                    g: 0,
+                                    b: 0,
+                                    alpha: 0
+                                }
+                            }) // 四边的透明区域
+                            .rotate(0)
+                            .toFile(extractedSmallPngSavePath, sharpCallback);
+                    }
+                }, () => {
+                    Editor.log(`There are ${spriteFrameNames.length} textures are generated!`);
+                    //start importing the generated textures folder
+                    Editor.Ipc.sendToMain('asset-db:import-assets', [extractedImageSaveFolder], Path.dirname(selectionUrl), true, (err) => {
+                        if (err) Editor.log('Importing assets error occurs: details' + err);
+
+                        Del(extractedImageSaveFolder, {
+                            force: true
+                        });
+                    }, -1);
+
+                }); // end of Async.forEach
+
+            } else {
+                Editor.Dialog.messageBox(dontSelectCorrectAssetMsg);
+            }
+        } else {
+            Editor.Dialog.messageBox(dontSelectCorrectAssetMsg);
+        }
+    },
+
+
+    // register your ipc messages here
+    messages: {
+        'unpack'() {
+            this.chaiPlist();
+        },
+    }
+}

package/unpack plist/package.json

@@ -0,0 +1,13 @@
+{
+  "name": "unpack-plist",
+  "version": "0.0.3",
+  "description": "A package for unpacking texture atlas created with TexturePacker.",
+  "author": "steven",
+  "main": "main.js",
+  "main-menu": {
+    "i18n:MAIN_MENU.package.title/unpack-plist/拆图": {
+      "message": "unpack-plist:unpack"
+    }
+  },
+  "_storeId": "3e72beb3934e4bea5f445520fd976a4c"
+}

package//345/274/225/347/224/250/346/237/245/346/211/276/345/231/250/CHANGELOG.md

@@ -0,0 +1,30 @@
+### 1.3.0.20210929
+
+1. 代码重构
+2. 引入 eazax 框架
+3. 查找性能大幅提升
+4. 文件解析优化，增强稳定性
+5. 去除「通过 uuid 查找」面板
+6. 加入检查更新机制
+
+
+
+### 1.2.0.20210405
+
+1. 修复“双开编辑器卡死”的问题
+2. 代码优化，提高查找速度
+3. 增加多语言（英语）支持
+4. 支持自定义快捷键（设置面板）
+
+
+
+### 1.1.0-20201112
+
+1. 增加“通过 uuid 查找”功能（新增面板）
+2. 优化代码
+
+
+
+### 1.0.0-20201103
+
+1. 首次发布

package//345/274/225/347/224/250/346/237/245/346/211/276/345/231/250/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2021 陈皮皮
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package//345/274/225/347/224/250/346/237/245/346/211/276/345/231/250/README.en.md

@@ -0,0 +1,111 @@
+# References Finder
+
+## Introduction
+
+[Cocos Creator Editor Extension]
+
+**Find asset references in seconds by one press.**
+
+
+
+## Open Source
+
+This extension is an open source project, here is the git repository: [https://gitee.com/ifaswind/ccc-references-finder](https://gitee.com/ifaswind/ccc-references-finder)
+
+If you like this project, don't forget to star [![star](https://gitee.com/ifaswind/ccc-references-finder/badge/star.svg?theme=dark)](https://gitee.com/ifaswind/ccc-references-finder/stargazers)!
+
+*If you have any usage problems, just create an issue on Gitee or add my WeChat `im_chenpipi` and leave a message.*
+
+
+
+## Screenshots
+
+![screenshot-1](https://gitee.com/ifaswind/image-storage/raw/master/repositories/ccc-references-finder/screenshot-1.png)
+
+![screenshot-2](https://gitee.com/ifaswind/image-storage/raw/master/repositories/ccc-references-finder/screenshot-2.png)
+
+![settings-panel](https://gitee.com/ifaswind/image-storage/raw/master/repositories/ccc-references-finder/settings-panel.png)
+
+
+
+## Environment
+
+Platform: Windows、macOS
+
+Engine: Cocos Creator 2.x
+
+
+
+## Download & Installation
+
+### Install from Cocos Store
+
+You can find this extension in Cocos Store now, click on *Extension -> Cocos Store* option to open the Cocos Store.
+
+Enter "**References Finder**" in the search bar, find it and then install it.
+
+![cocos-store](https://gitee.com/ifaswind/image-storage/raw/master/repositories/ccc-references-finder/cocos-store.png)
+
+*References Finder: [https://store.cocos.com/app/detail/2531](https://store.cocos.com/app/detail/2531)*
+
+
+
+### Download from git repository
+
+Click [here](https://gitee.com/ifaswind/ccc-references-finder/releases) or go to the release panel, download the latest version package of this extension.
+
+And then unzip the package:
+
+- Windows: Unzip to `C:\Users\${your username}\.CocosCreator\packages\`
+- macOS: Unzip to `~/.CocosCreator/packages/`
+
+For example, on my Windows computer, the full path of `package.json` file should be `C:\Users\Shaun\.CocosCreator\packages\ccc-references-finder\package.json`.
+
+
+
+## Usage
+
+### Find Asset References
+
+1. Select any asset(s) in Asset Panel.
+
+2. Press the hotkey (The default is `F6`) or click on *Extension -> References Finder -> Find Selected* option to find references.
+
+3. Then all references of asset would be printed on Console Panel.
+
+
+
+### Settings
+
+Click on *Extension -> References Finder -> Setting* option to open the setting panel.
+
+- **Show Details**: Show more details(node, component, property)
+- **Fold Result**: Fold result in one log
+
+In the **Hotkey** option, you can choose a hotkey(shortcut, for finding references of current selected asset) in preset list, or you can customize one in **Custom** option by yourself.
+
+One thing you should know, not every keys/keys-combinations can be used, because some keys/keys-combinations have been used by the system or Cocos Creator.
+
+*Accelerator reference: [https://www.electronjs.org/docs/api/accelerator](https://www.electronjs.org/docs/api/accelerator)*
+
+🥳 Enjoy!
+
+
+
+---
+
+
+
+# 公众号
+
+## 菜鸟小栈
+
+😺 我是陈皮皮，一个还在不断学习的游戏开发者，一个热爱分享的 Cocos Star Writer。
+
+🎨 这是我的个人公众号，专注但不仅限于游戏开发和前端技术分享。
+
+💖 每一篇原创都非常用心，你的关注就是我原创的动力！
+
+> Input and output.
+
+![](https://gitee.com/ifaswind/image-storage/raw/master/weixin/official-account.png)

package//345/274/225/347/224/250/346/237/245/346/211/276/345/231/250/README.md

@@ -0,0 +1,115 @@
+# 引用查找器
+
+## 介绍
+
+[Cocos Creator 编辑器扩展]
+
+**一键查找资源的所有引用，可精确到预制体或场景中的节点、组件和属性（不包括代码中的动态引用）。**
+
+
+
+## 开源
+
+本扩展项目完全开源，仓库地址：[https://gitee.com/ifaswind/ccc-references-finder](https://gitee.com/ifaswind/ccc-references-finder)
+
+如果你觉得这个项目还不错，请不要忘记点 [![star](https://gitee.com/ifaswind/ccc-references-finder/badge/star.svg?theme=dark)](https://gitee.com/ifaswind/ccc-references-finder/stargazers)！
+
+*如有使用上的问题，可以在 Gitee 仓库中提 Issue 或者添加我的微信 `im_chenpipi` 并留言。*
+
+
+
+## 截图
+
+![screenshot-1](https://gitee.com/ifaswind/image-storage/raw/master/repositories/ccc-references-finder/screenshot-1.png)
+
+![screenshot-2](https://gitee.com/ifaswind/image-storage/raw/master/repositories/ccc-references-finder/screenshot-2.png)
+
+![settings-panel](https://gitee.com/ifaswind/image-storage/raw/master/repositories/ccc-references-finder/settings-panel.png)
+
+
+
+## 运行环境
+
+平台：Windows、macOS
+
+引擎：Cocos Creator 2.x
+
+
+
+## 下载 & 安装
+
+### 扩展商店安装
+
+本扩展已上架 Cocos 商店，点击 Cocos Creator 编辑器顶部菜单栏中的 *扩展 -> 扩展商店* 即可打开扩展商店。
+
+在页面上方的搜索栏中搜索“**引用查找器**”就可以找到本插件，进入详情页即可直接安装（建议安装到全局）。
+
+![cocos-store](https://gitee.com/ifaswind/image-storage/raw/master/repositories/ccc-references-finder/cocos-store.png)
+
+*引用查找器：[https://store.cocos.com/app/detail/2531](https://store.cocos.com/app/detail/2531)*
+
+
+
+### 自行下载安装
+
+在[此处](https://gitee.com/ifaswind/ccc-references-finder/releases)或仓库发行版处下载最新的扩展压缩包。
+
+下载完成后将压缩包解压：
+
+- Windows：解压到 `C:\Users\${你的用户名}\.CocosCreator\packages\` 目录下
+- macOS：解压到 `~/.CocosCreator/packages/` 目录下
+
+以 Windows 为例，扩展的 `package.json` 文件在我的电脑上的完整目录为 `C:\Users\Shaun\.CocosCreator\packages\ccc-references-finder\package.json`。
+
+
+
+## 使用说明
+
+### 一键查找资源引用
+
+安装本扩展后，在资源管理器中选中任意资源，按下快捷键（默认为 `F6`）即可获取该资源的所有引用（不包括代码中的动态引用），结果将在控制台中以文本的方式打印出来。
+
+> 查找快捷键可进入扩展的设置面板进行修改
+
+
+
+### 设置
+
+点击编辑器顶部菜单栏中的 *扩展 -> 引用查找器 -> 设置* 即可打开扩展的设置面板。
+
+- **自动展开结果**：切换不同的结果展示方式（自动展开或手动展开）
+- **精确到组件属性**：引用信息精确到预制体或场景中的节点上的组件和属性（有的话）
+
+在设置面板中你可以更换快速查找引用的快捷键，也可以自定义一个自己喜欢的快捷键。
+
+不过需要注意的是，并非所有的按键都可以使用，因为有些快捷键已被系统或 Cocos Creator 占用。
+
+*键盘快捷键参考：[https://www.electronjs.org/docs/api/accelerator](https://www.electronjs.org/docs/api/accelerator)*
+
+
+
+---
+
+
+
+# 公众号
+
+## 菜鸟小栈
+
+😺 我是陈皮皮，一个还在不断学习的游戏开发者，一个热爱分享的 Cocos Star Writer。
+
+🎨 这是我的个人公众号，专注但不仅限于游戏开发和前端技术分享。
+
+💖 每一篇原创都非常用心，你的关注就是我原创的动力！
+
+> Input and output.
+
+![](https://gitee.com/ifaswind/image-storage/raw/master/weixin/official-account.png)
+
+
+
+## 游戏开发交流群
+
+皮皮创建了一个**游戏开发交流群**，供小伙伴们交流开发经验、问题求助和摸鱼（划掉）。
+
+感兴趣的小伙伴可以添加我微信 `im_chenpipi` 并留言 `加群`。