Highrez

1. Yes, with the portable version, you can run from a USB key or any folder on your machine, shared with other computers. The settings are held in an xml/xmbcs (still XML) file and nothing needs to be stored on the machine itself - in portable mode the settings are saved along side the executable, w...

Can you send me a copy of your profile so I can test with it here? Use the save profile button to save it and send me the file (either via PM or email it to me). It may shed some light on whats different with your settings compared to mine.

Hi,

Not really sure what in XMBC could cause that, unless you have changed the button behavior from default (particularly left click)?
What is you let button set to?

Its certainly not an issue here.
Does it happen only when XMBC is running?

That's handy to know.... It does sound like a problem XMBC is making worse... if you can ever figure out a reliable way to reproduce this, or get it captured in the debug log (as soon as it happens turn on debug logging and it should capture the last 100-220 events to the log file, I have a global h...

I know what you mean, I tend to default to simkeys too... I mean, I could add a tag to do it from there but it's probably not worth it in this case! Incidentally, I just tried on my other laptop with {LWIN}L and first time, it worked, and from then on, it hasn't worked. {LWIN}x works fine (and that'...

Have you tried anything else? Maybe instead of {holdms:500}{lmb} you could try {LMBD}{WAITMS:500}{LMBU} Or maybe {PRESS}{LMB}{WAITMS:500}{RELEASE}{LMB} (not sure about that one) The holdms option appeared to work here but its quite difficult to tell with {LMB} - I'll have to investigate further when...

Does it make any difference if you CTRL+ALT+DEL (then cancel from the security options screen) sometimes this fixes some windows issues? I cant say that I have noticed this particular bug before on Windows 10 or 11... You say its a bug in Windows than XMBC seems to trigger more - does it ever happen...

OK, but you haven't actually given a description of the problem....
Other than the title, which is rather vague, what exactly is the problem?

Does the following work?

Simulated keystrokes, method 6 (repeat) or method 7 depending on if you want to hold the button down or not...
{LMB}{WAITMS:100}{LMB}{WAITMS:100}{LMB}{WAITMS:100}{LMB}{WAITMS:100}{HOLDM:500}{LMB}

Did you intentionally leave the post template blank? Give me very little to go on!

I wonder if you could try the latest beta , its had a years worth of development since 2.20.5 and several things have been fixed and added. I would hate to spend a long time investigating this to find out I have fixed it already :)). However, I'm not sure I have fixed it already (if indeed it it is ...

Ive added this to the bug list, but can you explain a little more, what do you meant by "layer 2 only". There must still be a layer one?
Can you send me the example profile that does not work and explain how to reproduce it a little more?

Oh OK I didn't realize powertoys couldn't map to mouse actions... XMBC is designed to hook into the mouse message queue and then send stuff - it does not hook into the keyboard message queue (well other than for layer modifier keys). To add full keyboard support into XMBC is just far too much effort...

I guess it must be a protected key sequence... Why don't you just choose "Lock Workstation" instead of simulated keystrokes?

Sorry, XMBC is for configuring the mouse buttons, it can not re-map keyboard keys.
That would be a completely different program!

Maybe have a look at Microsoft Powertoys which has a keyboard key remapper