vncvr
May 16, 2020, 7:59pm
13
ggmanestraki:
I personally need to check if it is on or off before I use a macro that contains it, otherwise it messes things up. So I do a quick check, and then do the macro… I would absolutely %1000 despise not being able to check if it’s on or off, you would have to open up preferences to check which would take more time than erroneously using the macro when it’s in the wrong state, undoing the mistake, turning it on, and then re-applying the macro.
I need to be reminded too, when I’m the one issuing the commands. Buuut, when I fire a macro, I just expect it to do its job, as fast as possible. I don’t like the popup just then. The toggle state that the macro is presented with at its onset, I expect to be handled within the macro itself. I don’t want to have to take preparatory actions in order to launch a macro.
Without separate on/off for commands, or logical checks in macros, I don’t think the above is possible. But isn’t it elegant? Why do people ask for separate on/off commands? So that they can IGNORE the state of toggles!
So yes, it’s useful currently, but I’m looking forward to not having to be reminded toggle states because I can directly control them.
Agreed, if on/off commands come into existence (I have a feeling they will), then these messages won’t be needed - BUT - they should continue to exist for toggle commands. I hope Steinberg doesn’t remove toggles in place of on/off - both are useful… toggles taking up less keybinds. ie… I would be using On/Off without keybinds inside of macros, while having the toggle command version keybinded.
It should just be in a simple tree format.
-Toggle | keybind