I would love to see the addition of logic-based features in various parts of the Eos software.
For example, magic sheet object formatting:
If/then logic for conditional formatting
“If <[OSC Tx]> is <[Enabled]> then <[ObjectFill] [00F00]>”
Currently the way to do this is to use a toggle macro where there are two source macros and one target macro, using the macro color as the state indicator which gets swapped via said macros; however it is very possible for the indicator state to be inaccurate in the event that someone enabled or disabled using setup instead of the macros.
Expanding further:
Being able to use logic to check against current known states of various settings of the console as well as states of various target types, fields, etc would open up a whole world of useful functions - it could then be expanded into logic and conditional statements inside of macros too.
I can envision creating a library of features, settings, states, etc that could then be used inside of scripts or scriptlets embedded in things like magic sheet objects and macros. Essentially exposing the underlying database that is storing data to be able to use as a data source.
Another practical example - being able to remove the concept of needing to patch dummy channels for indicators. I recently programmed a TV studio with several zones, each with their own independent cue lists, all to be ran from a single magic sheet. In order to create visual indicators for which zones were currently active, I had to patch a dummy channel for each zone, and then make sure that channel was on in any cues for that zone, and then link that channel to a magic sheet object. Lots of layers of complexity and room for errors. Being able to use a small formatting script instead, such as “If <[CueList] [1]> is <[Active]> then <[ObjectFill] [00FF00]>” (of course, adding <else> as part of this would also be great.)
I have a LOT of ideas for this...
