Basically this patch uses the order in which the 'shift', 'ctrl', and 'alt' keys are pressed to create extra modifiers, which can be binded via the bus binds, or physically patched when using as a subpatch.
This is a subset of a greater set of modifiers I've been working on involving combinations of mouse keys, midi messages, touch-screen inputs, or basically whatever other messages are at hand, to enable me maximum control whatever 'position' I'm in within my setup.
There's a problem though, which is illustrated with this patch, and I'm unsure whether it is a related issue which is affecting progress with other things I'm working on.
Using the above patch, if I press first 'ctrl', then 'shift' and finally 'alt' the binds activate correctly, as well as deactivate when releasing them (in the same reversed order). So, the binds which output a value of '1' work as follows....
1) 'C'
2) 'C S' and '2 KEYS HELD'
3) 'C S A' and '3 KEYS HELD'
4) 'C S' and '2 KEYS HELD'
5) 'C'
However, if I press them in the order 'alt', 'ctrl', and 'shift' we get problems on the way down. Applying this in the same way as the previous 3 keys, when we get to step 5 (ie, when I should be left with a 'A' for 'alt') the binds 'A C' and '2 KEYS HELD' remain active. With 'shift', 'alt' then 'ctrl', this happens upon release of the third key. And 'alt', 'shift' then 'ctrl'. These all stay stuck until the mouse is moved.
Also, if I for example, have three keys held down, then move the mouse cursor to another window, or out of the current window, the order pressed is refreshed and replaced with 3 single keys instead.....
Any ideas? This happens using the virtual keyboard called by Usine, or the Windows touch-screen keyboard, or when using the real keyboard when either of these are showing (albeit much more problematic with the Usine virtual keyboard open). Using Usine's 'mouse' module leads to the same issues.
There are similar problems with the arrays of touch-screen inputs. Sometimes releasing a finger (at the array's end) results the size of the array (output from any type of module) reducing accordingly, and sometimes not. Upon releasing multiple 'touches' simultaneously, (or closer to) some will often remain.
Will HH2 resolve these, and/or should I do a bug report? Or any other helpful relevant info?
