-
Notifications
You must be signed in to change notification settings - Fork 26
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
Preset management #139
Comments
related to #140 |
if all the accessors are implemented, this could be starting as a cookbook example. If popular, can be made into a separate class. |
This should simply be |
wit the new MKtlDesc implementation, we could have a method |
yes, very good idea. |
💯 |
gogogo!!
|
MKtl(x).presetValuesAt(\sl) |
in many use cases, some controls should be saved, and others not (e.g. master volume). |
will try to get NamedList to do this nicely. |
wondering now how useful having presets of controller state is: |
I think this stems from me. What I suggested is that we should have the opportunity to easily freeze, store and later manage/sort the incomming data from controller(s) in order to I know that this can be done in many different ways and at different levels, but I think there should be a modality-specific approach to this. b
|
ok thanks, makes sense - just did a simple example for your use case, in ef8abe2. |
Moved this to Tutorials/Creating_Presets ... |
I'm also looking at implementing something like this. My use case is that I want to store all values of MKtlElements, so that when I reconnect the controller I can send the values back to the controller and recreate the previous state. I was thinking of storing a flat dictionary of keys to values, and naming the methods something like storeState loadState. Any comments ? Something like:
|
hi @miguel-negrao, |
E.g. by saving the state of an
MKtlElementGroup
and recalling it later.The text was updated successfully, but these errors were encountered: