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

Handle secondary history stack for specific tools #47

Open
sprocketc opened this issue Apr 2, 2022 · 0 comments
Open

Handle secondary history stack for specific tools #47

sprocketc opened this issue Apr 2, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@sprocketc
Copy link
Member

There are cases where we want to maintain a history of actions for a specific tool, but we don't want to add this state to our main history.

For instance, when we are trying to select multiple elements, being able to undo a selection would allow us to keep all of the previous actions instead of deselecting all elements and starting over.

Another example would be when we are drawing a polyline. We need to be able to go back and remove the added points step by step.

The tricky part would be to find a way to create a secondary action stack for such cases.
Although adding those action to our main history tree would work, it would create am extremely verbose history.
It would also make the history navigation harder and would increase the file size / memory footprint (see #26).

@sprocketc sprocketc self-assigned this Apr 2, 2022
@sprocketc sprocketc added this to the Pilot milestone Apr 2, 2022
@sprocketc sprocketc removed this from the Pilot milestone Oct 30, 2023
@sprocketc sprocketc added the enhancement New feature or request label Oct 11, 2024
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
Status: No status
Development

No branches or pull requests

1 participant