Please fill in this template when posting!
XMBC Version: 2.20.5
Installed or Portable version:installed
Windows Version: Windows11
Settings:
Appication:Default
Left Button:Button Held:(custom)
Action:Left Click
Held for 500ms:Double Click
Issue:
When I actually run it on Chrome, no events fire. (Firefox does not fire any events either).
Breakpoints are not detected by the double-click event in the development tool.
If I stop the mouse hook in the same environment and run it, it breaks normally.
JavaScript events are not firing.
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.
-
phil
- Site Admin
- Posts: 7897
- Joined: Sun Apr 06, 2003 11:12 pm
Re: JavaScript events are not firing.
Sorry, I'm not really sure I have a direct answer for that (Ive never noticed XMBC not working in browser, but I never really use the double click action).
Is it possible that the double click is too quick for chrome/firefox to recognize it? You could try simulated keystrokes and {lmb}{waitms:20}{lmb} to check that.
Other than that, I don't know why the injected inputs would not be triggering until you reinstall the mouse hook (that would suggest that Windows has removed the hook - it has a habit of doing that if the hook timeout is left at its default short value) but that would apply to any application, not just a browser? What is your hook timeout set to, and does increasing it (and rebooting) make any difference?
Is it possible that the double click is too quick for chrome/firefox to recognize it? You could try simulated keystrokes and {lmb}{waitms:20}{lmb} to check that.
Other than that, I don't know why the injected inputs would not be triggering until you reinstall the mouse hook (that would suggest that Windows has removed the hook - it has a habit of doing that if the hook timeout is left at its default short value) but that would apply to any application, not just a browser? What is your hook timeout set to, and does increasing it (and rebooting) make any difference?
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 11 x64 24H2, AMD Ryzen 9950x3D, MSI x870E Tomahawk, 64GB DDR%,
nVidia RTX 2070s (still lol)
--[ Administrator & XMBC Author ]--
Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 11 x64 24H2, AMD Ryzen 9950x3D, MSI x870E Tomahawk, 64GB DDR%,
nVidia RTX 2070s (still lol)
