Repository navigation
Add Rename and Set as start scene to scene context menus - #46
Merged
Merged
Conversation
JamieW105
added
type:feature
type:docs
area:engine
labels
ChatGPT Codex Connector
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Right-clicking a scene in Project → settings → Change scene now opens a submenu with Rename and Set as start scene. Right-clicking does not load the scene. Rename opens a dialog, retains the extension, saves active edits, moves backups/metadata, and updates the active path and start-scene reference; collisions or failed descriptor writes preserve the original files. Scene selection and undo history survive an active-scene rename.
Set as start scene persists an optional scene-relative
start_scenein project.engine and marks the list entry Start, without switching the active scene. Project opening honors that choice; older descriptors keep the main.scene/main.rscene default. Both actions require writable access and stop during play or runtime-change review. Play continues to use the active scene. A missing explicit start scene produces an error instead of creating an empty scene.Validation: 91 tests passed across engine-project, engine-editor, and rustic-editor, including clicks through the nested context menu, disabled actions, start-scene reopen with objects/environment, rename collision handling, and file rollback after configuration-save failure. Targeted Clippy with warnings denied, cargo fmt, and git diff --check passed. The required fresh Windows installer is being built by PR CI.
Companion website documentation: Rustic-Game-Engine/docs#56