I saw some of the layers have a "Revert automatically after [ ] seconds" option, and I was thinking if this makes possible to use double click functions.
Example:
You single-click button 4 and the layer switchs to layer 2, and also trigger a counter that would count to 0.3 seconds (timer is configurable)
If you click button 4 again before the counter runs out, it will trigger the double-click function, that will perform another thing, like Media-Mute.
Is this viable?
How about double-click functions?
Forum rules
Please read the forum rules before posting for the first time.
The more information you can provide, the quicker and more accurately someone can help.
NOTE: To reduce spam, new users can not post links, files or images until they have at least 4 posts.
Please read the forum rules before posting for the first time.
The more information you can provide, the quicker and more accurately someone can help.
NOTE: To reduce spam, new users can not post links, files or images until they have at least 4 posts.
Re: How about double-click functions?
Yes that should be possible... the problem right now is that selecting another layer on a click means the click will be swallowed. You could get around that using simulated keystrokes with {LMB}{LAYER:2} {RMB}{LAYER:2} etc. which would do the normal click and move to layer 2.
Another problem is that it would interfere with a genuine double click - so you probably dont want to do this the the primary left or right buttons!
In reality, you need to delay making a decision until you know if its a single click or a double click - and doing that is the problem. Its the same with button chording. You have to delay the first button until you know what was intended - and then perform the correct action. The problem with that, in user mode, is that simulating a normal mouse click can be problematic - many games for instance block injected keys and mouse buttons from the SendInput API that XMBC uses - so this delaying tactic would cause more harm than good in that situation. That, along with the potential requirement for a complete restructure is why I keep delaying this ability!
Thanks,
Phil
Another problem is that it would interfere with a genuine double click - so you probably dont want to do this the the primary left or right buttons!
In reality, you need to delay making a decision until you know if its a single click or a double click - and doing that is the problem. Its the same with button chording. You have to delay the first button until you know what was intended - and then perform the correct action. The problem with that, in user mode, is that simulating a normal mouse click can be problematic - many games for instance block injected keys and mouse buttons from the SendInput API that XMBC uses - so this delaying tactic would cause more harm than good in that situation. That, along with the potential requirement for a complete restructure is why I keep delaying this ability!
Thanks,
Phil
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 1Tb NVME, 2x2TB WD Black (RAID1)
--[ Administrator & XMBC Author ]--
Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 1Tb NVME, 2x2TB WD Black (RAID1)