Editor interface

PinK continues the core layout of the code editor and integrates resources, scenes, animations, previews and build portals into the same workspace.

Major regions

Left management level and resources, intermediate editing scene or code, right with Chat and Inspector, bottom view of diagnosis

• Title Toolbar: Select the scene, run a preview and open the building portal.
• Activity Bar and Game Sidebar: Toggle files, search, resource and hierarchy views.
• Editor area: open main.scene, ClickGame.ts, images, and animations.
• Chat and Inspect: Describe the task or check the currently selected nodes and components.
• Panel Area: View problems, outputs, terminals and debugging information.
• Status bar: project, language-service, and background-task status.

Use recommendations for interface

• When you are not familiar with the entrance, use the command panel first and do not use the icon to guess.
• Modify TargetSprite to first confirm the selected object in the hierarchy and then look at Inspector.
• When running failed, look first at the problem and the output panel, rather than restart the item immediately.
• Maintaining fixed window size, theme and project status for screenshot and problem recurrence.

Three perspectives of the same object

Take the example of TargetSprite: The resource view tells you where the picture comes from, the hierarchy and scene sheet tells you where the node is, and Inspector tells you which SpriteFrame was quoted by the Sprite component. Check each of these three places when checking " Do not show " ; check the GameController reference for ClickGame when clicking and counting.

The interface entry changes according to the project, the current editor and the functional status. When a button does not appear, confirm that the project has been initialized and opens a scene or file that satisfies the command condition.