Highrez

XMBC Version: 2.18.5
Windows Version: Windows 10 Pro 1803
Mouse Information (brand/model): Logitech M-U 0007
Computer Information:
Did the problem occur after an upgrade of XMBC?: No
Did the problem occur after a Windows update/upgrade?: No
How long have you used XMBC?: For years
What language and keyboard layout do you use in Windows?: German

Clear description of the problem:

Since 2019 and Win10 I use the "Active window on hover" feature and now it works pretty good.

But sometimes too good, because if I move the mouse a bit slowly over the screen a window in the background is activated.

E.g. I have a Solidworks window full screen, move the mouse to the taskbar, open a Windows Explorer and move the mouse to the Windows Explorer accross Solidworks. Means my issue occurs only if I have overlapping windows.

Therefore, I would like to ask for a delay (or something similar) to prevent premature activation.

Best regards,
Andreas.

Urm, it should be possible, actually I think there is already a delay but it will be a hard coded small number of milliseconds (!50) if there is.
I don't think exposing that and making it configurable will be too tricky but don't quote me on that. But if its possible, I presume you want it to work like a hover... so while the mouse is moving, keep resetting the delay timer, and only once the mouse has been stationary for X milliseconds should the activate command be sent?

I'll stick it on the list for the next version (2.19).

Just had a look there is already a delay of 150ms.
So in 2.19 I will increase that default delay to 250ms but you will be able to change that in the settings file (I'm not going to make it show in the GUI for various reasons0.

Great!

Is it already included in beta5?

I have it that activated just for specific windows. Will it be configurable globally or for specific windows?

Max

I think it wen tin to beta 1 (bug id 637) so yes its there.
Its global and in the XML settings, the element is ActivateOnMouseOver and the attribute is Delay (the value is in milliseconds - default: 250ms)

Great, found it. Thanks!