8000 Undo/Redo · Issue #490 · nudibranchrecords/hedron · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Undo/Redo #490

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
Open
funwithtriangles opened this issue Jan 22, 2025 · 0 comments
Open

Undo/Redo #490

funwithtriangles opened this issue Jan 22, 2025 · 0 comments

Comments

@funwithtriangles
Copy link
Member

User created changes to state should be stored in a history, with the ability to undo/redo.

We don't want to record everything, however. Think of all the changes happening with audio or LFO inputs.

Midi is a bit of a grey area, some users may want to undo a value change made with a midi device, other may not, especially if they're doing something weird like sequencing from other software. Ideally we have a setting for this.

In an ideal world, we could have some LFO going off, while the user is making changes. They could then undo all their changes and the LFO keeps smoothly going. Unfortunately I feel like the default behaviour with a library like zundo is that the snapshot is saved of the whole state at that time and so the LFO would jump around as the user uses undo/redo. Maybe not though...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@funwithtriangles
0