Skip to content
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

Implement undo support #15

Open
myrsloik opened this issue May 9, 2022 · 0 comments · Fixed by Jaded-Encoding-Thaumaturgy/Wobbly#2
Open

Implement undo support #15

myrsloik opened this issue May 9, 2022 · 0 comments · Fixed by Jaded-Encoding-Thaumaturgy/Wobbly#2

Comments

@myrsloik
Copy link
Collaborator

myrsloik commented May 9, 2022

The basics are already done in the undo_feature branch. Help welcome.

arch1t3cht added a commit to arch1t3cht/Wobbly that referenced this issue Apr 9, 2023
This works by simply keeping backups the entire relevant state of the
Wobbly project after each action and rolling back to such states on
undo/redo. This is feasible since Wobbly's internal state is not very
memory-intensive.

A drawback is that all list or table models have to be repopulated from
scratch, so selections in dialogs are cleared on every undo/redo. This
could be improved later on by saving the UI state before a rollback and
restoring it after it is completed.

Fixes dubhater#15 .
arch1t3cht added a commit to arch1t3cht/Wobbly that referenced this issue Apr 17, 2023
This works by simply keeping backups the entire relevant state of the
Wobbly project after each action and rolling back to such states on
undo/redo. This is feasible since Wobbly's internal state is not very
memory-intensive.

A drawback is that all list or table models have to be repopulated from
scratch, so selections in dialogs are cleared on every undo/redo. This
could be improved later on by saving the UI state before a rollback and
restoring it after it is completed.

Fixes dubhater#15 .
Setsugennoao pushed a commit to Jaded-Encoding-Thaumaturgy/Wobbly that referenced this issue Apr 17, 2023
This works by simply keeping backups the entire relevant state of the
Wobbly project after each action and rolling back to such states on
undo/redo. This is feasible since Wobbly's internal state is not very
memory-intensive.

A drawback is that all list or table models have to be repopulated from
scratch, so selections in dialogs are cleared on every undo/redo. This
could be improved later on by saving the UI state before a rollback and
restoring it after it is completed.

Fixes dubhater#15 .
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant