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.

Sign up for GitHub

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

Jump to bottom

Each project should contain separate undo stack #9

Open

vt4a2h opened this issue Oct 21, 2018 · 0 comments

Assignees

Labels

Owner

vt4a2h commented Oct 21, 2018

In the current implementation we have only one undo stack for all projects. This potentially lead to inconsistency and memory leaks.

Acceptance criteria:

Separate undo stack should be created per project
When active project has changed, current command stack should be changed as well
When project is closed, its undo stack should be dropped as well
Command for changing active project shouldn't be added to any undo stack at all
Deactivated project should retain its modified state (and all other states)

vt4a2h added the enhancement label

vt4a2h self-assigned this

vt4a2h added a commit that referenced this issue


          Issue #9: initial implementation of ProjectFactory class

f00a9db

vt4a2h added a commit that referenced this issue


          Issue #9: fixed CMake builds

0eb9809

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment