![]() ![]() if you disable my left mouse button (up and down movement) for a shor period of time after a mouse up.that's what I attempted, but it didn't work yet. You can clearly see that the mouse send another click, Lbutton down and up.occasionally it only sends another Down, without an Up, which is odd, but I probably need to code for it. AHK_L isn't bad at all, this script just fails in it.Īnd now i get what the test results mean the numbers is how far i moved the mouse along the x/y axis (or something like that).actually it's the "or something like that".it's how many milliseconds (ms) since the last mouse event.Īs you can see, i moved the mouse quite a lot in the last test.no, as per above, it just means you clicked more slowly.possibly due to moving the mouse farther, but it technically isn't about how far the mouse moved, just how long it took since the last event (if you leave the mouse in one position & click slowly, you can test this). It seems you were right now i dont get those wierd symbols.I really need to test it in AHK_L & fix that issue. In the result bellow i louched first the Buggy-mouse then the analyzer.OK, perhaps one more log with them launched the other way? (I don't know which way is "better" I'm just trying to test).or just wait for the next version. So, instead of all that, it might be easier to wait for the next version. But really, I plan on adding logging to Buggy-Mouse.ahk to overcome this uncertainty (then there wouldn't be 2 scripts potentially fighting for the mouse hook). You don't have to, but if you want: Start Buggy, then Start Analyzer, make a log, exit both scripts, then do it the other way: Start Analyzer & then Start Buggy, make a log. Now when it comes to your analyzer, you told me that it matters which script i lounch first.I said that since both scripts use the mouse hook it might matter which is started 1st. ![]() Then you can disable the "double-click fix" & focus only on the "click after mouse up fix".then only re-enable the "double-click fix" if you still experience that problem (there's no reason for the code to be attempting to "fix" something that your mouse isn't actually doing). Just to recap: Your mouse does have BOTH bugs? right? Bug 1: it will double-click when you try to single-click?.& ALSO.Bug 2: it will click again on mouse up? In the next version of Buggy-Mouse.ahk, I plan to make each bug-fix optional so you can have any combination of fixes active. I will try to follow the logic of the script more closely & see if I can get it to block the correct thing & not block too much (like you say it is doing). ![]() when the bug from my mouse happens the left mouseclick gets disabled until i push the left mousebutton a couple of times.I added the "extra" blocking quickly & couldn't test it (& still can't), I'll try again soon. "Updated: Sun, Jul 10, 2011".just a small request: Please include the entire "Updated" date when referring to a version. Seems like a good test, now, if I could just make my mouse "mess up" like that I could test it 1st hand & get it fixed! ![]() i click and hold the left mouse button then i mark a text.thx for that, I just wanted to know how you were testing. Cutting my code down to a script with a few lines is NOT gonna provide the same functionality. Buggy-Mouse.ahk is big & complicated.1) for debugging & 2) for making it function. An example with ahk ( doubleclick works only when click twice slow ).simplifying the code down to that is not gonna work. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |