8 hours ago
(11 hours ago)bplus Wrote: BTW @Pete double clicks from your demo seems like needs work.
Honestly, I don't think it should be the responsibility of a mouse checking routine to report double clicks; it should be something coded in the end program that function is included in.
Think about it for a moment: What IS a double click??
Nothing more than two clicks done within some set interval. If I have a slow timer, then it might be two clicks in a whole second. click...click... double click. If it's a fast time, you might have spam those two clicks to create a "double click" in 0.01 seconds... One set mouse routine shouldn't set that for you; that should be in the end-program itself which tracks that time and decides how short a gap and how to handle a "double click".
I used to try and code mouse functions to report double clicks and triple clicks and hold events and drag events... and then I decided that was just overkill. 99.99% of programs don't need all that junk. Let those that do, code for it *specifically* inside themselves. Mouse up/down/click. That's enough for a good mouse function to be truly useful. Anything else is just overkill.
