About the double-click function, as I can see when you release the button at the first click on a given file, the file gets selected and then after the release at the second click it gets opened, so it looks more like 'sequential clicking' (with the same button) instead of chording, which requires the second button to be pressed before the first one is released. So I guess that your suggestion about the drop time might work for such kind of 'sequential click' feature which in fact is not a bad idea. It probably would be limited to double-/triple- click with the same button (coz maybe a sequence of different buttons would be quite messy) but still it would give some good options and especially to those with 3-button mice. To be honest, at the moment my mouse sometimes eats up my left clicks so very often I end up tripple-clicking to get a decent double-click and I can tell it's quite easy when you get used to it.ChowGuy wrote:Ie, If you have "button chording" assigned, the the initial button (or any action assigned as "default") does not get seen until you release it. Admittedly this mostly affects button1 [drag] button2 [mouse gestures] and maybe button3 for some applications, but for those who have only three-button mice to begin that's a major limitation.
That was pretty much the point of my suggesting a drop time in which to detect a second action or abandon the mapping, much like the existing "Double-Click Speed" option.
On the whole though, it's working well, thanks.
Now about the blocked 'first button pressed' message, I was hoping that there would be a 'Block original mouse input' option so the user can decide for himself whether to block it or not. Obviously when you want to use chording most probably you will have to make some compromise about the initial button (in order to use it for several commands instead of only one) but there are many cases when you might allow the 'first button pressed' message to pass so you wouldn't lose its functionality while you also use it for chording. In fact today I tested the chording in a game which uses 'RMB hold down' for dynamic change of viewpoint and I was amazed that it works just perfectly . Somehow the game receives the 'RMB held down' message and I am able to change the view and when I press the 2-nd button - the chord is also executed . While in SolidWorks when I use the Middle button for chording I am not able to change the view at all. On the other hand the idea about the time delay may succeed if the actual blocking is delayed for say 200 ms and if no 2-nd click in that interval - the 'first button pressed' message is passed through and XMBC doesn't expect 2-nd click any more. (Maybe that was what ChowGuy meant )
And one more thing, if the second button is released before releasing the first one - the chord is executed and nothing else happens, but if you release the second button after the first one is released - the chord gets executed and then the original action of that second button gets executed too even when 'Block original mouse input' is enabled (which I think should not happen).