For an existing Issue Tracker FT: --------------------------------- It would be useful (and rational) to have a full set of Actions to modify every 2-state variable that can be changed. That is:Set to state A Set to state B Toggle state This is done for some variables now, such as: -- relative grid snap -- all envelopes for (all) tracks But it should be extended to all similar variables. At different times you want to set the variable, unset it or toggle it. ------------------------------------------------ This might extended to N-state variables too: -- Set to state A -- Set to state B -- Set to state C -- Set to state D -- Set to Next state (and cycle round) -- Set to Previous state (and cycle round)
For the 2-state variable, I may not always want to Toggle it (as I do not know what its current state is), but force it to be State A (e.g. Off") or State B (e.g. "On"). "Unset" is not needed as either "Set" actions effectively unsets the other state. So all three are needed. -------------------- "Rings" are something else, I think. Perhaps I used the wrong term, though.
Of course, that is why I asked for a few examples. So far I did not want to use those cases, maybe after reading your examples I might consider also trying them.
I see the point in this FR, but just out of interest... Wouldn't the action list get huge then (I mean it IS quite huge already). I don't have an overview, are there lots missing or only a few ? (again, not speaking against this FR, just curious)
I do not have an overview, too. :) I bookmarked this: Usually I just visit that page and search there, then even if Reaper is not running you can check actions for availability or just for ideas, what could be combined with what else. The maximum action number is known already: 16bit.