[bug oder feature?] Win10 login screen

[Sosborses]

Please fill in this template when posting! okay
XMBC Version: 2.19.2
Installed or Portable version: installed, me stupid, I no
Windows Version: 10.0.19045.7184
Mouse Information (brand/model): not telling, but has planned obsolescence rubber on it and it's sticky now, I hate it (-> baby powder;)
Relevant Computer Information (CPU, RAM etc): very obsolete, but I like it, it barely overheats under load, keeps me warm during winter
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?: years and years (not the ghai British band)
What language and keyboard layout do you use in Windows?: variable, sometimes even Cyrillic

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).:
1.) I paid pennies for this piece of great SW to some east-Asian dude back in the day, and I just noticed you guys bought him out. What kind of name is agent 'Gibbons' anyway?
2.) Let me tell you a joke:
Little Red Riding Hood meets a wolf in the forest. It goes:
- I am the Thunderbolt-endowed wolf, prepare to suffer!
- OMG, will it hurt?
- Did it?

This is my situation exactly.
If I'm quick enough, no problems. I hate girls telling me I'm too quick.
If I'm slow at the Win10 login screen, your app takes away the focus from the password text field.
I have to press CTRL+ALT+DEL to re-focus, like back in the day, or fiddle with the TAB crap that changes with every Windows version since Ballmer.

If this is on purpose forget what I just typoed.
k thx

ps: pls do not sell the user data if you ever execute your exit plan

[phil]

Sorry, I don't know what the f**k are you talking about for the majority of that post?! I guess you are trying to be funny... It didn't work - maybe I need some more sleep!

XMBC is my software, it has always been MY software since I started it way back in 2004(ish) when Microsoft first released Windows XP (x64 edition) and they and Logitech failed to provide working button configuration software. I have never bought it from anyone, taken if over from anyone, nor have I ever charged for it - AND I still have the source code going back to day one. Oh and Gibbons is MY surname, nothing more - sorry if that offends you!

Neither do I store or intend to do anything with "user data" - not sure what you even mean by "user data", maybe other than the logon details to this forum - that's the most I "collect" in order for people to make crazy posts such as this one!

Frankly, it sounds like you have been scammed already if you paid anything to anyone for XMBC (other than donations which are just that). Are you sure you have the right software?! There are plenty of people, illegitimately trying to pass XMBC off as their own, including hosting fake (but very legitimate websites hosting my files). As a hobbyist, there is not a lot I can do about that. I don't have lawyers nor the time to spend chasing all that to no avail, and, at the end of the day, if people are not prepared to check what they are downloading, nor where from that's on them, not me. I already go out of my to devote my spare time to XMBC and to obtain the digital signatures to sign the software as required by Microsoft - that's about the extend of what I can do.

Finally, as for the bug... I'm not sure I understand.
Firstly, XMBC does not start until you have logged in to your session. So I guess you mean the "logon screen" after your session locks when you have been away, or maybe after waking from sleep... At that time, XMBC will be running. However, as the lock screen is a protected (session 0) screen, XMBC can not inject keys into it (as far as I am aware)... Unless, just maybe you have disabled UAC? Perhaps things are different then, I'm not sure to be fair. Certainly when I check here, simulated keys are are not working on my lock screen (Windows 11).

How have you setup your button mappings? Maybe that will give me a clue...