09-24-2007, 04:18 PM
Hi,
It seems like this is not already part of QM. There is "optional follow by" but this doesn't allow you to have both single and double keypresses as separate triggers.
This is actually important since many devices need to map keyboard sequences for their extra "mouse buttons" e.g. if you want a trigger to be double click mouse button 6 (mapped to Ctrl-Alt-1), you would need to have someway for QM to distinguish between CA1 clicked twice in fast succession and single press.
Looking at the code for mouse-chords (which already contains functionality for double clicking the triggering key), this seems like it should be possible to convert this code to that. But I wouldn't know how to do it without losing the ability to distinguish between single and double (and perhaps triple?) clicks (actually keypresses).
Don't want to make extra work for you Gintaras, just want to see what you think...or if there is an answer already out there that I couldn't find...
Thanks,
Stuart
It seems like this is not already part of QM. There is "optional follow by" but this doesn't allow you to have both single and double keypresses as separate triggers.
This is actually important since many devices need to map keyboard sequences for their extra "mouse buttons" e.g. if you want a trigger to be double click mouse button 6 (mapped to Ctrl-Alt-1), you would need to have someway for QM to distinguish between CA1 clicked twice in fast succession and single press.
Looking at the code for mouse-chords (which already contains functionality for double clicking the triggering key), this seems like it should be possible to convert this code to that. But I wouldn't know how to do it without losing the ability to distinguish between single and double (and perhaps triple?) clicks (actually keypresses).
Don't want to make extra work for you Gintaras, just want to see what you think...or if there is an answer already out there that I couldn't find...
Thanks,
Stuart