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

Don't participate in REAPER's undo #915

Closed
helgoboss opened this issue Feb 4, 2024 · 0 comments
Closed

Don't participate in REAPER's undo #915

helgoboss opened this issue Feb 4, 2024 · 0 comments
Labels
enhancement New feature or request realearn Related to ReaLearn

Comments

@helgoboss
Copy link
Owner

helgoboss commented Feb 4, 2024

Invoking undo in REAPER after changes within ReaLearn can lead to unpleasant surprises because not each little change within ReaLearn is reported to REAPER (that would be resource-consuming but also difficult to do correctly because ReaLearn's state is naturally captured by REAPER's undo system due to its nature as VST plug-in).

ReaLearn and Playtime should be considered as its own "undo universe". Each Playtime Matrix already has its own undo history. And ReaLearn will probably also get its own one at some point.

That's why I want to ignore REAPER-undo-system-triggered state changes. With REAPER >= v7.09+dev0202 this is possible.

@helgoboss helgoboss added the enhancement New feature or request label Feb 4, 2024
helgoboss added a commit that referenced this issue Feb 4, 2024
needs REAPER >= v7.09+dev0202
@helgoboss helgoboss added the realearn Related to ReaLearn label Jul 25, 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 realearn Related to ReaLearn
Projects
None yet
Development

No branches or pull requests

1 participant