I guess I could use the input code a certain number of times in the macro depending on which input it is currently set atUnless you have discrete Input Codes, that's the only way to do it. You will need to put a delay between each 'Input' in the action list.
but that number will change all the time.True, but if you make a jump to the new Input Device's Panel with other buttons to go to OTHER Devices, you will be at a known state prior to pressing any NEW Input change.
In other words, for each Device, you have a panel that you will be jumping *from* when you change Inputs. This Panel will have a button for each of your OTHER Devices to push to go to those other Devices (Inputs).
When you are on Device (Input) 1 - you know where you are in the scrolling. When you press the Button for Device (Input) 3, you know that you need to have 2 Input Actions in the Action list for that Button in order to go to Device (Input) 3, ending with a jump to the Panel for Device (Input) 3.
On **THIS** Panel you need buttons for Devices 1, 2, 4 (no 3, because you are already there). And as a result you now know where you are *currently* in the scrolling sequence and can then program each of these buttons accordingly.
This can be problematic if someone changes inputs some other way, which will then screw up your sequencing. Sometimes pressing Channel Up + however many number of inputs is the best way. By using CH UP you know where you are in the Input sequence. You might get a 'flicker' of something you don't want on the screen, but . . . OH WELL!
Think about it, and try it. It WILL work. It's just not as elegant as Discrete Codes.
MIKE