-
-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a undo/redo history log #953
Comments
This is already sort of implemented. When you do anything with a scene in the editor, a message is printed to the console, telling you which property you edited. Rather than calling it an undo log, let's call it an action history. This already-implemented editor feature can be edited to include the action history on a per-scene basis. Maybe this history can be saved to a dotfile (similar to |
Hm, the logging may be implemented, but when I hit Ctrl+Z a couple times, I have no idea "where" I am in the history. Knowing where I am is the main purpose of such a panel or visualization. The added bonus of being able to just click on any undo state (or "action") as shown in the gif above would be another very desirable UX improvement. |
Note that it might actually be possible to get the editor's UndoRedo and display a panel which displays the actions stored in that UndoRedo, all inside a plugin. I do agree that it might be nicer to have it out of the box, however. |
Imo this wouldn't be very useful without implementing this #1630 |
Describe the project you are working on: This applies to any game or project
Describe the problem or limitation you are having in your project:
I don't know which action I can undo and which action I can't undo. Jumping back and forth in the undo history is anything but transparent or user friendly.
Describe the feature / enhancement and how it helps to overcome the problem or limitation:
A panel with a history log for all undoable steps. Branching undo tree would be amazing, but a linear list would already be a great improvement.
Issue moved here from godotengine/godot#25919
Describe how your proposal will work, with code, pseudocode, mockups, and/or diagrams:
If this enhancement will not be used often, can it be worked around with a few lines of script?:
I don't think so.
Is there a reason why this should be core and not an add-on in the asset library?:
It's a core usability feature.
The text was updated successfully, but these errors were encountered: