XMBC Version: v2.19.2
Windows Version: Windows 10 64 bit
Mouse Information (brand/model): Kensington Orbit Fusion (trackball)
Relevant Computer Information (CPU, RAM etc): Intel i7 9750H; nVidia GTX 1660 Ti; 16GB RAM
Did the problem occur after an upgrade of XMBC? (If so, from what version?): no
Did the problem occur after a Windows update/upgrade? (If so, from what version?): no
How long have you used XMBC?: 1 week
What language and keyboard layout do you use in Windows?: US layout; Dutch and US-English languages
Clear description of the problem - try and include as much information as possible, including what button and mappings you are having problems with (if applicable).:
I have set button 5 to execute double click, and noticed that in AutoCAD it is behaving a bit glitchy. It sometimes behaves as if its clicking 3 times, and sometimes as if its clicking only once, and sometimes it cancels my selection or command as if I had pressed ESC.
I have found that I can work around the problem with a simulated keystroke: {LMB}{WAITMS:10}{LMB} with method 1.
If I use {LMB} with method 9, or {LMB}{LMB} with method 1, I get the same glitchy behaviour as the standard double click method. {LMB}{LMB} works if I set delay between keystrokes to 10ms in settings. So it seems that the regular double click is too fast for AutoCAD to interpret, and a slight delay of 10ms solves the issue.
Just thought I would put this out there for anyone who's using AutoCAD (or potentially any other software that behaves funky with double click).
Double click glitchy in AutoCAD
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: Double click glitchy in AutoCAD
Rather than add the WAITMS in each command, you could just adjust the global "delay between simulated keystrokes" in the advanced settings tab. This should apply to the "double click" action too (although I'm not 100% sure about that without checking the code).
EDIT: Oh I see you have tried that and it worked. I guess the default is just a little too slow for Autocad on YOUR computer (it will depend on the speed of your processor, how the target application behaves and anything else going on at the time, so the defaults are a bit of a guess - although I'm a bit surprised on a recent I7!).
EDIT: Oh I see you have tried that and it worked. I guess the default is just a little too slow for Autocad on YOUR computer (it will depend on the speed of your processor, how the target application behaves and anything else going on at the time, so the defaults are a bit of a guess - although I'm a bit surprised on a recent I7!).
--[ 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)
Re: Double click glitchy in AutoCAD
Yeah, I did try setting the global delay to 10ms. That works for simulated keystroke {LMB}{LMB}, but it has no effect on the normal double click (or at least not as experienced in AutoCAD).
EDIT: I might add that I'm on AutoCAD 2014, so that might have something to do with it.
EDIT: I might add that I'm on AutoCAD 2014, so that might have something to do with it.
Re: Double click glitchy in AutoCAD
OK, its possible that the globaly setting isn't being used in the "double click" option - I'll have to look into that - it must have a hard coded delay (or none at all) but it does effectively do the same thing as simkeys {LMB}{LMB} internally so I'm a bit surprised!
--[ 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)
Re: Double click glitchy in AutoCAD
I had the same problem in explorer on Windows 10. "Double click" on button 4 of my mouse wouldn't register as a double click, but pretty much exclusively on folders. It would sometimes do a single click (just select the folder) or make the folder name editable (as in two spaced out single clicks).
XMBC (version 2.13) worked well on the same hardware under Windows 7, but after an upgrade to Windows 10 (yes, I'm a bit late to that party on this hardware) it showed this issue (still the exact same XMBC 2.13). Since it mostly happened to folders, where Windows does some "fancy" stuff for the info tooltips when hovering, I disabled those. I had already done that on 7 as well, even before I ever used XMBC, because I found them annoyingly useless (for the less than 1% of cases when I want to know something about a folders contents I use the properties dialog). So the problem likely would have been there already as well with the tooltips.
This made the double single-clicks much less frequent, but they still occurred. The newest version of XMBC didn't change that either. But setting {LMB}{WAITMS:10}{LMB} instead of "double click" for button 4 fixed it (what was about one or two out of 10 double clicks glitching before, didn't happen at all in the last 2 hours). Thanks for the hint Wimads
!
It doesn't seem to be a very common problem (I only found this thread mentioning it, but that could also be my search terms
). It could still be a good idea though to insert the "delay between simulated keystrokes" for hardcoded actions as well, because if someone needs the global delay it will most likely be needed in double clicks as well.
XMBC (version 2.13) worked well on the same hardware under Windows 7, but after an upgrade to Windows 10 (yes, I'm a bit late to that party on this hardware) it showed this issue (still the exact same XMBC 2.13). Since it mostly happened to folders, where Windows does some "fancy" stuff for the info tooltips when hovering, I disabled those. I had already done that on 7 as well, even before I ever used XMBC, because I found them annoyingly useless (for the less than 1% of cases when I want to know something about a folders contents I use the properties dialog). So the problem likely would have been there already as well with the tooltips.
This made the double single-clicks much less frequent, but they still occurred. The newest version of XMBC didn't change that either. But setting {LMB}{WAITMS:10}{LMB} instead of "double click" for button 4 fixed it (what was about one or two out of 10 double clicks glitching before, didn't happen at all in the last 2 hours). Thanks for the hint Wimads
![Cheers :cheers:](./images/smilies/cheers.gif)
It doesn't seem to be a very common problem (I only found this thread mentioning it, but that could also be my search terms
![Surprised :o](./images/smilies/icon_surprised.gif)
Re: Double click glitchy in AutoCAD
After more than a month of trying, I have to report that unfortunately the WAITMS did not solve the problem as I initially thought. The simulated double clicks seem to work correctly in all programs, except the one where it's most important for me: Windows Explorer.
Double clicks aren't recognized half the time. If it happens they seem to not work at all for a few seconds. I click the 4th mouse button (set to {LMB}{WAITMS:50}{LMB}), nothing happens. I click it again, nothing happens. I often have to repeat the click several times (5 times an more) in a row, before a double click is executed. Sometimes the filename starts to become editable (suggesting Explorer sees two single clicks instead of one double click). At other times double clicks work 5 times in a row...
I tried a lot of things in the setting, changing the WAITMS to higher numbers, block original mouse input, send in another thread, on button press or release, with realtime process priority, aso. Nothing changed the glitchy behaviour, not even in how often it occurs.
![Sad :(](./images/smilies/icon_sad.gif)
Double clicks aren't recognized half the time. If it happens they seem to not work at all for a few seconds. I click the 4th mouse button (set to {LMB}{WAITMS:50}{LMB}), nothing happens. I click it again, nothing happens. I often have to repeat the click several times (5 times an more) in a row, before a double click is executed. Sometimes the filename starts to become editable (suggesting Explorer sees two single clicks instead of one double click). At other times double clicks work 5 times in a row...
I tried a lot of things in the setting, changing the WAITMS to higher numbers, block original mouse input, send in another thread, on button press or release, with realtime process priority, aso. Nothing changed the glitchy behaviour, not even in how often it occurs.
Re: Double click glitchy in AutoCAD
Very odd - not something I can reproduce here... (nor last time you mentioned this in Oct).
Are you really still on 2.13? if so, have you tried the latest version?
Maybe if you could turn on debug logging - and then capture it failing and ideally working in the log - make a not of the time that it failed and succeeded (because debug log is VERY verbose). But not a lot of point doing the debug logging on 2.13 as that's so old, much will have changed since then which would make diagnosis (and tracing through the code) pretty diffcult - 2.19.2 would be much better log wise - even that is quite old now, but at least its the latest released version - I do have some internal builds but I don't think they will make any difference here although I confess Ive only tried this on the latest internal builds - so its always possible Ive fixed something (esp. since 2.13 but even possible since 2.19.2).
Also - what spec if your hardware? Ive tried on various systems here but they are all pretty high spec.
Are you really still on 2.13? if so, have you tried the latest version?
Maybe if you could turn on debug logging - and then capture it failing and ideally working in the log - make a not of the time that it failed and succeeded (because debug log is VERY verbose). But not a lot of point doing the debug logging on 2.13 as that's so old, much will have changed since then which would make diagnosis (and tracing through the code) pretty diffcult - 2.19.2 would be much better log wise - even that is quite old now, but at least its the latest released version - I do have some internal builds but I don't think they will make any difference here although I confess Ive only tried this on the latest internal builds - so its always possible Ive fixed something (esp. since 2.13 but even possible since 2.19.2).
Also - what spec if your hardware? Ive tried on various systems here but they are all pretty high spec.
--[ 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)
Re: Double click glitchy in AutoCAD
More than half a year later...
Yes, I've always used 2.19.2 for all my tests (and am still using it). My computer is a i5-3570K, old but enough for all I do and should be able to handle mouse clicks
. I have enabled debug logging and compared occasions when it didn't work with working ones. I couldn't really find any differences except for slightly reordered messages (but never consistently reordered considering working vs. non-working).
I hope I cut the logs at the right positions: at the first mouse-over of the Explorer window up until a "Finished" message. After that there were other mouse-overs of mouse moves, that didn't seem relevant to the problem anymore.
Here are entries when it did work:
Here when it didn't:
I can't really see any difference. It's like Explorer just doesn't get or process one of the simulated inputs it is sent. Would there be a way for XMBC to check if an input has been processed?
Yes, I've always used 2.19.2 for all my tests (and am still using it). My computer is a i5-3570K, old but enough for all I do and should be able to handle mouse clicks
![Wink :wink:](./images/smilies/icon_wink.gif)
I hope I cut the logs at the right positions: at the first mouse-over of the Explorer window up until a "Finished" message. After that there were other mouse-overs of mouse moves, that didn't seem relevant to the problem anymore.
Here are entries when it did work:
Code: Select all
06-08-2022 12:35:08.054> ProcessMouseOverTimerProc: Checking MouseOver(2267,614)...
06-08-2022 12:35:08.054> GetProcessIntegrityLevel for PID 5268 returned 0x00002000
06-08-2022 12:35:08.054> GetProcessName(7 WindowFromHWND): Got name for PID 5268, 'explorer.exe' for HWND 0x00262B40 using GetProcessImageFileName
06-08-2022 12:35:08.054> GetProcessName result 1 time 0ms
06-08-2022 12:35:08.054> FindAppSettings: Matching profile not found.
06-08-2022 12:35:08.054> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 150ms - ID 00005988
06-08-2022 12:35:08.202> ProcessMouseOverTimerProc: Checking MouseOver(2322,460)...
06-08-2022 12:35:08.202> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 150ms - ID 00005987
06-08-2022 12:35:08.370> ProcessMouseOverTimerProc: Checking MouseOver(2325,437)...
06-08-2022 12:35:08.439> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 150ms - ID 00005986
06-08-2022 12:35:08.602> ProcessMouseOverTimerProc: Checking MouseOver(2233,297)...
06-08-2022 12:35:08.602> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 150ms - ID 00005983
06-08-2022 12:35:08.755> ProcessMouseOverTimerProc: Checking MouseOver(2202,271)...
06-08-2022 12:35:08.771> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 150ms - ID 00005982
06-08-2022 12:35:08.917> ProcessMouseOverTimerProc: Checking MouseOver(2197,251)...
06-08-2022 12:35:08.924> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 150ms - ID 00005981
06-08-2022 12:35:09.087> ProcessMouseOverTimerProc: Checking MouseOver(2194,245)...
06-08-2022 12:35:09.118> MouseHookLLProc: MouseHookData: Msg=0x020b (WM_XBUTTONDOWN), X=2194, Y=245, Data=0x00010000, Flags=0x00000000, Time=520224187, Info=0x0, Ptr=0xEB106E1, Layer=0
06-08-2022 12:35:09.118> Translating XLeft Button Down Key state 0x0: Action 28 [Simulated Keys '{LMB}{WAITMS:100}{LMB}' (thread-down)]
06-08-2022 12:35:09.118> SendInput::SendMouse: Queue mouse button='Left', Action='Down', Point=2194,245, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:35:09.118> SendInput::SendMouse: Queue mouse button='Left', Action='Up', Point=2194,245, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:35:09.118> SendInput::SendMouse: Queue mouse button='Left', Action='Down', Point=2194,245, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:35:09.118> SendInput::SendMouse: Queue mouse button='Left', Action='Up', Point=2194,245, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:35:09.118> MouseHookLLProc: Removing message 0x020B (2194,245) from mouse hook queue as we have overridden it.
06-08-2022 12:35:09.118> CSendInput::ProcessQueue: Starting to process 5 queue entries
06-08-2022 12:35:09.118> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:35:09.125> MouseHookLLProc: MouseHookData: Msg=0x0201 (WM_LBUTTONDOWN) Injected, X=2194, Y=245, Data=0x00000000, Flags=0x00000001, Time=520224187, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:35:09.125> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:35:09.125> MouseHookLLProc: Passing original mouse message 00000201 through....
06-08-2022 12:35:09.125> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:35:09.140> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:35:09.140> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:35:09.140> MouseHookLLProc: MouseHookData: Msg=0x0202 (WM_LBUTTONUP) Injected, X=2194, Y=245, Data=0x00000000, Flags=0x00000001, Time=520224187, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:35:09.140> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:35:09.140> MouseHookLLProc: Passing original mouse message 00000202 through....
06-08-2022 12:35:09.156> CSendInput::ProcessQueue: Sleeping for 100ms
06-08-2022 12:35:09.187> MouseHookLLProc: MouseHookData: Msg=0x020c (WM_XBUTTONUP), X=2194, Y=245, Data=0x00010000, Flags=0x00000000, Time=520224265, Info=0x0, Ptr=0xEB106E1, Layer=0
06-08-2022 12:35:09.187> Translating XLeft Button Up Key state 0x0: Action 28 [Simulated Keys '{LMB}{WAITMS:100}{LMB}' (thread-down)]
06-08-2022 12:35:09.187> MouseHookLLProc: Removing message 0x020C (2194,245) from mouse hook queue as we have overridden it.
06-08-2022 12:35:09.187> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 300ms - ID 0000597F
06-08-2022 12:35:09.256> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:35:09.256> MouseHookLLProc: MouseHookData: Msg=0x0201 (WM_LBUTTONDOWN) Injected, X=2194, Y=245, Data=0x00000000, Flags=0x00000001, Time=520224187, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:35:09.256> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:35:09.256> MouseHookLLProc: Passing original mouse message 00000201 through....
06-08-2022 12:35:09.256> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:35:09.272> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:35:09.272> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:35:09.272> MouseHookLLProc: MouseHookData: Msg=0x0202 (WM_LBUTTONUP) Injected, X=2194, Y=245, Data=0x00000000, Flags=0x00000001, Time=520224187, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:35:09.272> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:35:09.272> MouseHookLLProc: Passing original mouse message 00000202 through....
06-08-2022 12:35:09.287> CSendInput::ProcessQueue: Finished sending 5 queue entries... (Flushed = 0)
06-08-2022 12:40:48.619> ProcessMouseOverTimerProc: Checking MouseOver(2224,505)...
06-08-2022 12:40:48.619> GetProcessName(7 WindowFromHWND): Called for the same PID 5268 [] but as it is explorer.exe, we will check anyway HWND 0x00710B86
06-08-2022 12:40:48.619> GetProcessIntegrityLevel for PID 5268 returned 0x00002000
06-08-2022 12:40:48.619> GetProcessName(7 WindowFromHWND): Got name for PID 5268, 'explorer.exe' for HWND 0x00710B86 using GetProcessImageFileName
06-08-2022 12:40:48.619> GetProcessName result 1 time 0ms
06-08-2022 12:40:48.619> FindAppSettings: Matching profile not found.
06-08-2022 12:40:48.619> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 150ms - ID 000056C3
06-08-2022 12:40:48.789> ProcessMouseOverTimerProc: Checking MouseOver(2246,357)...
06-08-2022 12:40:48.789> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 150ms - ID 000056C2
06-08-2022 12:40:48.936> ProcessMouseOverTimerProc: Checking MouseOver(2220,277)...
06-08-2022 12:40:48.936> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 150ms - ID 000056C1
06-08-2022 12:40:49.105> ProcessMouseOverTimerProc: Checking MouseOver(2220,263)...
06-08-2022 12:40:49.105> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 150ms - ID 000056C0
06-08-2022 12:40:49.268> ProcessMouseOverTimerProc: Checking MouseOver(2215,246)...
06-08-2022 12:40:49.490> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 150ms - ID 000056BD
06-08-2022 12:40:49.522> MouseHookLLProc: MouseHookData: Msg=0x020b (WM_XBUTTONDOWN), X=2215, Y=245, Data=0x00010000, Flags=0x00000000, Time=520564593, Info=0x0, Ptr=0xEB106E1, Layer=0
06-08-2022 12:40:49.522> Translating XLeft Button Down Key state 0x0: Action 28 [Simulated Keys '{LMB}{WAITMS:100}{LMB}' (thread-down)]
06-08-2022 12:40:49.522> SendInput::SendMouse: Queue mouse button='Left', Action='Down', Point=2215,245, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:40:49.522> SendInput::SendMouse: Queue mouse button='Left', Action='Up', Point=2215,245, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:40:49.522> SendInput::SendMouse: Queue mouse button='Left', Action='Down', Point=2215,245, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:40:49.522> SendInput::SendMouse: Queue mouse button='Left', Action='Up', Point=2215,245, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:40:49.522> MouseHookLLProc: Removing message 0x020B (2215,245) from mouse hook queue as we have overridden it.
06-08-2022 12:40:49.522> CSendInput::ProcessQueue: Starting to process 5 queue entries
06-08-2022 12:40:49.522> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:40:49.522> MouseHookLLProc: MouseHookData: Msg=0x0201 (WM_LBUTTONDOWN) Injected, X=2215, Y=245, Data=0x00000000, Flags=0x00000001, Time=520564593, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:40:49.522> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:40:49.522> MouseHookLLProc: Passing original mouse message 00000201 through....
06-08-2022 12:40:49.537> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:40:49.537> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:40:49.537> MouseHookLLProc: MouseHookData: Msg=0x0202 (WM_LBUTTONUP) Injected, X=2215, Y=245, Data=0x00000000, Flags=0x00000001, Time=520564593, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:40:49.537> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:40:49.537> MouseHookLLProc: Passing original mouse message 00000202 through....
06-08-2022 12:40:49.537> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:40:49.553> CSendInput::ProcessQueue: Sleeping for 100ms
06-08-2022 12:40:49.622> MouseHookLLProc: MouseHookData: Msg=0x020c (WM_XBUTTONUP), X=2215, Y=245, Data=0x00010000, Flags=0x00000000, Time=520564703, Info=0x0, Ptr=0xEB106E1, Layer=0
06-08-2022 12:40:49.622> Translating XLeft Button Up Key state 0x0: Action 28 [Simulated Keys '{LMB}{WAITMS:100}{LMB}' (thread-down)]
06-08-2022 12:40:49.622> MouseHookLLProc: Removing message 0x020C (2215,245) from mouse hook queue as we have overridden it.
06-08-2022 12:40:49.637> ProcessMouseOverTimerProc: Checking MouseOver(2215,245)...
06-08-2022 12:40:49.653> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:40:49.669> MouseHookLLProc: MouseHookData: Msg=0x0201 (WM_LBUTTONDOWN) Injected, X=2215, Y=245, Data=0x00000000, Flags=0x00000001, Time=520564593, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:40:49.669> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:40:49.669> MouseHookLLProc: Passing original mouse message 00000201 through....
06-08-2022 12:40:49.669> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:40:49.675> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:40:49.675> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:40:49.675> MouseHookLLProc: MouseHookData: Msg=0x0202 (WM_LBUTTONUP) Injected, X=2215, Y=245, Data=0x00000000, Flags=0x00000001, Time=520564593, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:40:49.675> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:40:49.675> MouseHookLLProc: Passing original mouse message 00000202 through....
06-08-2022 12:40:49.675> CSendInput::ProcessQueue: Finished sending 5 queue entries... (Flushed = 0)
06-08-2022 12:40:51.194> ProcessMouseOverTimerProc: Checking MouseOver(2198,251)...
06-08-2022 12:40:51.294> MouseHookLLProc: MouseHookData: Msg=0x020b (WM_XBUTTONDOWN), X=2198, Y=251, Data=0x00010000, Flags=0x00000000, Time=520566375, Info=0x0, Ptr=0xEB106E1, Layer=0
06-08-2022 12:40:51.294> Translating XLeft Button Down Key state 0x0: Action 28 [Simulated Keys '{LMB}{WAITMS:100}{LMB}' (thread-down)]
06-08-2022 12:40:51.294> SendInput::SendMouse: Queue mouse button='Left', Action='Down', Point=2198,251, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:40:51.294> SendInput::SendMouse: Queue mouse button='Left', Action='Up', Point=2198,251, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:40:51.294> SendInput::SendMouse: Queue mouse button='Left', Action='Down', Point=2198,251, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:40:51.294> SendInput::SendMouse: Queue mouse button='Left', Action='Up', Point=2198,251, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:40:51.294> MouseHookLLProc: Removing message 0x020B (2198,251) from mouse hook queue as we have overridden it.
06-08-2022 12:40:51.294> CSendInput::ProcessQueue: Starting to process 5 queue entries
06-08-2022 12:40:51.294> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:40:51.310> MouseHookLLProc: MouseHookData: Msg=0x0201 (WM_LBUTTONDOWN) Injected, X=2198, Y=251, Data=0x00000000, Flags=0x00000001, Time=520566375, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:40:51.310> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:40:51.310> MouseHookLLProc: Passing original mouse message 00000201 through....
06-08-2022 12:40:51.310> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:40:51.326> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:40:51.326> MouseHookLLProc: MouseHookData: Msg=0x0202 (WM_LBUTTONUP) Injected, X=2198, Y=251, Data=0x00000000, Flags=0x00000001, Time=520566375, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:40:51.326> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:40:51.326> MouseHookLLProc: Passing original mouse message 00000202 through....
06-08-2022 12:40:51.326> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:40:51.326> CSendInput::ProcessQueue: Sleeping for 100ms
06-08-2022 12:40:51.410> MouseHookLLProc: MouseHookData: Msg=0x020c (WM_XBUTTONUP), X=2198, Y=251, Data=0x00010000, Flags=0x00000000, Time=520566484, Info=0x0, Ptr=0xEB106E1, Layer=0
06-08-2022 12:40:51.410> Translating XLeft Button Up Key state 0x0: Action 28 [Simulated Keys '{LMB}{WAITMS:100}{LMB}' (thread-down)]
06-08-2022 12:40:51.410> MouseHookLLProc: Removing message 0x020C (2198,251) from mouse hook queue as we have overridden it.
06-08-2022 12:40:51.410> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 300ms - ID 000056B6
06-08-2022 12:40:51.426> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:40:51.426> MouseHookLLProc: MouseHookData: Msg=0x0201 (WM_LBUTTONDOWN) Injected, X=2198, Y=251, Data=0x00000000, Flags=0x00000001, Time=520566375, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:40:51.426> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:40:51.426> MouseHookLLProc: Passing original mouse message 00000201 through....
06-08-2022 12:40:51.442> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:40:51.442> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:40:51.442> MouseHookLLProc: MouseHookData: Msg=0x0202 (WM_LBUTTONUP) Injected, X=2198, Y=251, Data=0x00000000, Flags=0x00000001, Time=520566375, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:40:51.442> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:40:51.442> MouseHookLLProc: Passing original mouse message 00000202 through....
06-08-2022 12:40:51.442> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:40:51.457> CSendInput::ProcessQueue: Finished sending 5 queue entries... (Flushed = 0)
Code: Select all
06-08-2022 12:33:42.545> ProcessMouseOverTimerProc: Checking MouseOver(2207,381)...
06-08-2022 12:33:42.545> GetProcessName(7 WindowFromHWND): Called for the same PID 5268 [] but as it is explorer.exe, we will check anyway HWND 0x00262B40
06-08-2022 12:33:42.545> GetProcessIntegrityLevel for PID 5268 returned 0x00002000
06-08-2022 12:33:42.545> GetProcessName(7 WindowFromHWND): Got name for PID 5268, 'explorer.exe' for HWND 0x00262B40 using GetProcessImageFileName
06-08-2022 12:33:42.545> GetProcessName result 1 time 0ms
06-08-2022 12:33:42.545> FindAppSettings: Matching profile not found.
06-08-2022 12:33:42.545> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 150ms - ID 00005A46
06-08-2022 12:33:42.707> ProcessMouseOverTimerProc: Checking MouseOver(2197,447)...
06-08-2022 12:33:42.745> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 150ms - ID 00005A45
06-08-2022 12:33:42.892> MouseHookLLProc: MouseHookData: Msg=0x020b (WM_XBUTTONDOWN), X=2203, Y=458, Data=0x00010000, Flags=0x00000000, Time=520137968, Info=0x0, Ptr=0xEB106E1, Layer=0
06-08-2022 12:33:42.892> Translating XLeft Button Down Key state 0x0: Action 28 [Simulated Keys '{LMB}{WAITMS:100}{LMB}' (thread-down)]
06-08-2022 12:33:42.892> SendInput::SendMouse: Queue mouse button='Left', Action='Down', Point=2203,458, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:33:42.892> SendInput::SendMouse: Queue mouse button='Left', Action='Up', Point=2203,458, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:33:42.892> SendInput::SendMouse: Queue mouse button='Left', Action='Down', Point=2203,458, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:33:42.892> SendInput::SendMouse: Queue mouse button='Left', Action='Up', Point=2203,458, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:33:42.892> MouseHookLLProc: Removing message 0x020B (2203,458) from mouse hook queue as we have overridden it.
06-08-2022 12:33:42.892> CSendInput::ProcessQueue: Starting to process 5 queue entries
06-08-2022 12:33:42.892> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:33:42.892> MouseHookLLProc: MouseHookData: Msg=0x0201 (WM_LBUTTONDOWN) Injected, X=2205, Y=459, Data=0x00000000, Flags=0x00000001, Time=520137968, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:33:42.892> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:33:42.892> MouseHookLLProc: Passing original mouse message 00000201 through....
06-08-2022 12:33:42.892> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:33:42.908> ProcessMouseOverTimerProc: Checking MouseOver(2203,458)...
06-08-2022 12:33:42.915> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:33:42.915> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:33:42.915> MouseHookLLProc: MouseHookData: Msg=0x0202 (WM_LBUTTONUP) Injected, X=2207, Y=460, Data=0x00000000, Flags=0x00000001, Time=520137968, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:33:42.915> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:33:42.915> MouseHookLLProc: Passing original mouse message 00000202 through....
06-08-2022 12:33:42.915> CSendInput::ProcessQueue: Sleeping for 100ms
06-08-2022 12:33:43.003> MouseHookLLProc: MouseHookData: Msg=0x020c (WM_XBUTTONUP), X=2210, Y=462, Data=0x00010000, Flags=0x00000000, Time=520138078, Info=0x0, Ptr=0xEB106E1, Layer=0
06-08-2022 12:33:43.003> Translating XLeft Button Up Key state 0x0: Action 28 [Simulated Keys '{LMB}{WAITMS:100}{LMB}' (thread-down)]
06-08-2022 12:33:43.003> MouseHookLLProc: Removing message 0x020C (2210,462) from mouse hook queue as we have overridden it.
06-08-2022 12:33:43.003> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 300ms - ID 00005A44
06-08-2022 12:33:43.015> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:33:43.015> MouseHookLLProc: MouseHookData: Msg=0x0201 (WM_LBUTTONDOWN) Injected, X=2210, Y=462, Data=0x00000000, Flags=0x00000001, Time=520137968, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:33:43.015> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:33:43.015> MouseHookLLProc: Passing original mouse message 00000201 through....
06-08-2022 12:33:43.015> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:33:43.030> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:33:43.030> MouseHookLLProc: MouseHookData: Msg=0x0202 (WM_LBUTTONUP) Injected, X=2210, Y=462, Data=0x00000000, Flags=0x00000001, Time=520137968, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:33:43.030> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:33:43.030> MouseHookLLProc: Passing original mouse message 00000202 through....
06-08-2022 12:33:43.030> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:33:43.030> CSendInput::ProcessQueue: Finished sending 5 queue entries... (Flushed = 0)
06-08-2022 12:43:21.746> ProcessMouseOverTimerProc: Checking MouseOver(2276,482)...
06-08-2022 12:43:21.746> GetProcessName(7 WindowFromHWND): Called for the same PID 5268 [] but as it is explorer.exe, we will check anyway HWND 0x004C25CA
06-08-2022 12:43:21.746> GetProcessIntegrityLevel for PID 5268 returned 0x00002000
06-08-2022 12:43:21.746> GetProcessName(7 WindowFromHWND): Got name for PID 5268, 'explorer.exe' for HWND 0x004C25CA using GetProcessImageFileName
06-08-2022 12:43:21.746> GetProcessName result 1 time 0ms
06-08-2022 12:43:21.746> FindAppSettings: Matching profile not found.
06-08-2022 12:43:21.746> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 150ms - ID 000054B9
06-08-2022 12:43:21.878> MouseHookLLProc: MouseHookData: Msg=0x020b (WM_XBUTTONDOWN), X=2303, Y=535, Data=0x00010000, Flags=0x00000000, Time=520716953, Info=0x0, Ptr=0xEB106E1, Layer=0
06-08-2022 12:43:21.878> Translating XLeft Button Down Key state 0x0: Action 28 [Simulated Keys '{LMB}{WAITMS:100}{LMB}' (thread-down)]
06-08-2022 12:43:21.878> SendInput::SendMouse: Queue mouse button='Left', Action='Down', Point=2303,535, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:43:21.878> SendInput::SendMouse: Queue mouse button='Left', Action='Up', Point=2303,535, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:43:21.878> SendInput::SendMouse: Queue mouse button='Left', Action='Down', Point=2303,535, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:43:21.878> SendInput::SendMouse: Queue mouse button='Left', Action='Up', Point=2303,535, MouseHookPtr=0xEB106E1, Delay=10
06-08-2022 12:43:21.878> MouseHookLLProc: Removing message 0x020B (2303,535) from mouse hook queue as we have overridden it.
06-08-2022 12:43:21.878> CSendInput::ProcessQueue: Starting to process 5 queue entries
06-08-2022 12:43:21.878> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:43:21.878> MouseHookLLProc: MouseHookData: Msg=0x0201 (WM_LBUTTONDOWN) Injected, X=2303, Y=535, Data=0x00000000, Flags=0x00000001, Time=520716953, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:43:21.878> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:43:21.878> MouseHookLLProc: Passing original mouse message 00000201 through....
06-08-2022 12:43:21.878> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:43:21.893> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:43:21.893> MouseHookLLProc: MouseHookData: Msg=0x0202 (WM_LBUTTONUP) Injected, X=2303, Y=535, Data=0x00000000, Flags=0x00000001, Time=520716953, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:43:21.893> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:43:21.893> MouseHookLLProc: Passing original mouse message 00000202 through....
06-08-2022 12:43:21.893> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:43:21.893> CSendInput::ProcessQueue: Sleeping for 100ms
06-08-2022 12:43:21.909> ProcessMouseOverTimerProc: Checking MouseOver(2303,535)...
06-08-2022 12:43:21.994> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:43:21.994> MouseHookLLProc: MouseHookData: Msg=0x0201 (WM_LBUTTONDOWN) Injected, X=2303, Y=539, Data=0x00000000, Flags=0x00000001, Time=520716953, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:43:21.994> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:43:21.994> MouseHookLLProc: Passing original mouse message 00000201 through....
06-08-2022 12:43:21.994> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:43:22.009> MouseHookLLProc: MouseHookData: Msg=0x020c (WM_XBUTTONUP), X=2303, Y=539, Data=0x00010000, Flags=0x00000000, Time=520717078, Info=0x0, Ptr=0xEB106E1, Layer=0
06-08-2022 12:43:22.009> Translating XLeft Button Up Key state 0x1: Action 28 [Simulated Keys '{LMB}{WAITMS:100}{LMB}' (thread-down)]
06-08-2022 12:43:22.009> MouseHookLLProc: Removing message 0x020C (2303,539) from mouse hook queue as we have overridden it.
06-08-2022 12:43:22.009> TimerThread[0xB00]: Started MOUSE OVER timer 1015 for 300ms - ID 000054B8
06-08-2022 12:43:22.009> CSendInput::ProcessQueue: Sending 1 SIMULATED INPUTS
06-08-2022 12:43:22.009> MouseHookLLProc: MouseHookData: Msg=0x0202 (WM_LBUTTONUP) Injected, X=2303, Y=539, Data=0x00000000, Flags=0x00000001, Time=520716953, Info=0xEB106E1, Ptr=0xEB106E1, Layer=0
06-08-2022 12:43:22.009> MouseHookLLProc: Ignoring mouse message injected by XMBC
06-08-2022 12:43:22.009> MouseHookLLProc: Passing original mouse message 00000202 through....
06-08-2022 12:43:22.009> CSendInput::ProcessQueue: Sleeping for 10ms
06-08-2022 12:43:22.025> CSendInput::ProcessQueue: Finished sending 5 queue entries... (Flushed = 0)
Re: Double click glitchy in AutoCAD
I tried this but it doesn't seem to change anything. Maybe my mouse click setting only applies to the buttons and not the wheel? Also it seems to zoom to extents if I've held the wheel for too long while panning. Maybe I'm accidentally clicking it still. Thanks for the idea.