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

[version 3.x] History #36

Open
maoschanz opened this issue Dec 12, 2019 · 0 comments
Open

[version 3.x] History #36

maoschanz opened this issue Dec 12, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@maoschanz
Copy link
Owner

maoschanz commented Dec 12, 2019

This idea actually requires to change the architecture of the code: the data model shall be distinct from the view, since there are 2 possible different views

undo/redo is done in the model, and once it has finished its shit, the model calls the view to update it

@maoschanz maoschanz added the enhancement New feature or request label Dec 12, 2019
maoschanz referenced this issue Dec 26, 2019
because it'll not be compatible with my first attempt to implement an undo/redo history
maoschanz added a commit that referenced this issue May 7, 2020
poor designs are easy

issue #36
@maoschanz maoschanz changed the title undo/redo [version 3.x] History Jul 26, 2021
@maoschanz maoschanz pinned this issue Jul 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant