Is your feature request related to a problem? Please describe.
In the config editor, moves are currently tied to their current scene, and there is no direct way to reorganize them by moving one or more move(s) to another scene. This makes it slower to refactor demo flows while editing, especially when scenes evolve and moves need to be regrouped.
Describe the solution you'd like
Add support in the config editor to move selected move(s):
- To an existing scene
- To a new scene (created as part of the move action)
Suggested behavior:
- Provide a context action (e.g., right-click or command palette) such as Move to scene...
- Let users choose an existing target scene, or select/create New scene and provide a title/id
- Preserve move order when moving multiple moves
- Update the underlying file structure accordingly
- Keep schema validity intact after the move operation
Describe alternatives you've considered
- Manually cut/paste moves in the source file and fix indentation/order
- Recreate moves in the target scene and delete originals
These workarounds are error-prone and less efficient than a dedicated editor action.
Additional context
This would complement existing scene/move editing capabilities and improve authoring workflows for larger demos where restructuring is common.
Is your feature request related to a problem? Please describe.
In the config editor, moves are currently tied to their current scene, and there is no direct way to reorganize them by moving one or more move(s) to another scene. This makes it slower to refactor demo flows while editing, especially when scenes evolve and moves need to be regrouped.
Describe the solution you'd like
Add support in the config editor to move selected move(s):
Suggested behavior:
Describe alternatives you've considered
These workarounds are error-prone and less efficient than a dedicated editor action.
Additional context
This would complement existing scene/move editing capabilities and improve authoring workflows for larger demos where restructuring is common.