-
Notifications
You must be signed in to change notification settings - Fork 432
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
Undo / Redo History Function #741
base: develop
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Undo Redo Logic sollte komplett gekapselt sein
- Scopes: Mode, Drawing Mode, Global
- GlobalReverting should be ModeReverting
- New GlobalRevert across everything
- pm:edit/drag/etc ->
createChangeOnLayer
- addHistoryEntry, removeHistoryEntry, getHistory
- Transactions vs Snapshots: Consistency in Applying and Storing
- Architektur: global History with EVERYTHING (one array), then filter based on
Kontext
[
{
diff: `theChange`,
layer: `<layerRef>`
mode: `Removal/Edit/etc`
action: `Draw/Move/Drag/...`
}
]
where does this feature stands? |
@t1a2l it is currently on hold because we don't have the time to develop it |
Any chance of this getting merged and published soon? |
@winston01 no |
Are there any updated on this feature? |
Any update on this feature? |
@Falke-Design Hey, any ETA on this feature? it is in development since 2020. It is the only feature keeping me from moving from leafelt draw to this plugin. |
@t1a2l sorry to hear that but sadly we have this feature currently not on our roadmap. |
This feature is under development!
Having lots of tests from different people would be nice
Fix: #320