That you sometimes offer support too is kinda mind blowing.
So thank you.
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).:Posting template
Installed or Portable version: Installed
Windows Version: Win 10 Pro
Mouse Information (brand/model): Kensington Orbit
Relevant Computer Information (CPU, RAM etc): Intel(R) Pentium(R) CPU G3258 @ 3.20GHz 3.20 GHz 8Gbs RAM
Did the problem occur after an upgrade of XMBC? (If so, from what version?): No problem. More a functionality question.
Did the problem occur after a Windows update/upgrade? (If so, from what version?): No problem. More a functionality question.
How long have you used XMBC?: Forever? Feels like. Over so many PCs (mine and families)
What language and keyboard layout do you use in Windows?: US Eng
Feels similar to this thread: viewtopic.php?t=4006
In FTL game [SPACE] is the pause button.
Built a simulated keystroke series to allow quick pause/unpause cycle limiting player movement to a couple of frames on screen where I can reassess.
Works perfectly but only (roughly) 50% of the time.Left button sim keystroke:
6: As button is held down
Framing it as EVEN/ODD = On/off = green light/red light cycle, *if* the moment of release happens to be on an ODD number of pauses XBMC invoked, I'm in serious trouble or dead. EVEN number of invocations, I'm safely back into pause "safety" again.
I feel like what is happening is random probability has my key release ending on an ODD number of pauses pressed about 50% of the time which puts me in harms way.
A compromise that may work is forcing another cycle but, as I don't see how XBMC can know where I came off the button as an odd number of presses or even, I don't see an obvious solution which is why I'm brainstorming for help.
I DO need the functionality of the held down state to save me repetitive stress harm (it works perfectly when I am willing to tap the mouse button using the 1: when pressed option but if the avatar movement cycle needs to run 7+ seconds, the volume of presses is taxing on the fingers/tendons/etc.) Retaining hold functionality necessity is where I'm lost in the jungle.
Feels like I'm so close or not seeing the problem from the right angle to zero in on the solution.