Allow me to start from scratch.
The vision switcher desk in question logs all button pushes, down to the millisecond.
As the 'top' layer of buttons is not enough for some functions such as macros, a fairly standard style of shift is employed. There are other items that are shifted, but Macros are the only buttons of interest to me in this regard.
While some buttons are in fact held down, then while held another button pushed, such as using shifting on buttons, they are unable to be logged thus and in fact are logged as single instances independently and consecutively, with the shift operator (e.g. MACRO 2ND SHIFT) prior to the button that needed shifting.
This also means if two buttons are pressed simultaneously they are simply logged in the order that the desk was able to identify whichever might have been milliseconds after the other. This then becomes an issue with the other levels of shift. There are four levels in total - one unshifted and 3 shifted.
This is an unfortunate limitation I need to do my best to work with, and will lead to some errors where say shift might be pressed simply to see what is underneath (the buttons are contextually labeled with an LCD screen per button) without actually then pushing any significant button afterwards, as it was not held.
So on my table I have identified the 4 possible macro levels as this:
Button/MACRO NO SHIFT________________(No shift buttons are employed)
MACRO 2ND SHIFT_____________________(The button MACRO 2ND SHIFT is held down, before the button to shift)
MACRO 3RD SHIFT_____________________(The button MACRO 3RD SHIFT is held down, before the button to shift)
MACRO 4TH SHIFT_____________________(The 2 buttons MACRO 2ND SHIFT and MACRO 3RD SHIFT are held down before the button to shift)
For the 4th level - the two shift buttons may appear in the log list in either order, as clearly fingers aren't robotic, but if they are together, chances are it is 4th. (Although in fact you could look on the 2nd level, then the third level for something, yet then push the top level; but I can only work with what I've got).
So - while my conversion works great (Sheet LOG) for all top level functions, anywhere it logs a button after 2nd, 3rd, or 2nd and 3rd in any order, it should refer to a different column in the table.
I have now filled all of these columns out if they are not macro shifted buttons, so if one pushes 2nd for a look but then does't follow up with a macro button, but something unrelated, it will still at least show that button correctly.
See latest attachment. I hope that long winded mess doesn't leave you more confused.
Thanks!
Paul
Bookmarks