[BUG] Mouse clicks unfocusing window

[Pieplup]

Please fill in this template when posting!
XMBC Version:
Installed or Portable version:
Windows Version:
Mouse Information (brand/model):
Relevant Computer Information (CPU, RAM etc):
Did the problem occur after an upgrade of XMBC? (If so, from what version?):
Did the problem occur after a Windows update/upgrade? (If so, from what version?):
How long have you used XMBC?:
What language and keyboard layout do you use in Windows?:

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).:

[phil]

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

[Pieplup]

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

It must've gotten deleted or something
Please fill in this template when posting!
XMBC Version: 2.20.15
Installed or Portable version: Installed
Windows Version: Windows 11 Pro 22h2
Mouse Information (brand/model):Logitech g203
Relevant Computer Information (CPU, RAM et c): Intel i3 1125G4 2.0ghz
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?: about a year
What language and keyboard layout do you use in Windows?: US English
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).: So there's this bug in windows, which if you click a window it becomse unfocused it seems to autofocus on a specific iwndow and XMBC triggers this all the time. and there isn't really a good way to fix except to restart the computer. It's to the point where like after 3 hours it happens, and its' made me stop using the software.

[phil]

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?

[Pieplup]

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?

I edited it

[phil]

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 when XMBC is not running?
I wonder if there is something else you are running that makes it worse or some configuration difference from standard?

[Pieplup]

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 when XMBC is not running?
I wonder if there is something else you are running that makes it worse or some configuration difference from standard?

Well certain applications trigger, it. XMBC triggers it alot, It can sometimes be fixed by closing applications. I'll see if that works next tiem it happens.

[Pieplup]

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 when XMBC is not running?
I wonder if there is something else you are running that makes it worse or some configuration difference from standard?

CTRL+ALT+DELETE DOes seem tow ork thanks

[phil]

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 hotkey setup to toggle debug logging on and off which helps here, but it does not always highlight anything obvious unfortunately) send it over (along with the rough timestamp it went wrong) and it might help pinpoint the problem.