XMBC Beta 2.20

[Darktemp]

Hi, I installed 2.20 Beta 11 (and updated to 2.20 Beta 12) because I was also affected by the "Firefox 110" update.
The scrolling issue is fixed, thanks!
But that Firefox version (currently installed: "110.0 (64-Bit)") also breaks the function "Forward" and "Back" which I remapped.

My mouse has by default "Button 4=Back" and "Button 5=Forward" and I remapped it that "Button 5=Back" (and Button 4 is Double Click).

I didn't check every function, but e.g. "Double Click", "Enter" and "Escape" works, but other browser functions like "stop/refresh/fav/search" also don't work.

Is this a similar issue like the scrolling problem?

Here is a log snippet:
at 17:45:10 I clicked the button 5 in a normal explorer-window and the 'back' function works
at 17:45:17, I did the same in the firefox window but firefox ignores it

Code: Select all

17-02-2023 17:45:09.253> TimerThread[0xCE0]: Started MOUSE OVER timer 1015 for 150ms - ID 00005582
17-02-2023 17:45:09.407> ProcessMouseOverTimerProc: Checking MouseOver(1594,1670)...
17-02-2023 17:45:09.407> GetProcessName(7 WindowFromHWND): Called for the same PID 8448 [] but as it is explorer.exe, we will check anyway HWND 0x00010D7C
17-02-2023 17:45:09.407> GetProcessIntegrityLevel for PID 8448 returned 0x00002000
17-02-2023 17:45:09.407> GetProcessName(7 WindowFromHWND): Got name for PID 8448, 'explorer.exe' for HWND 0x00010D7C using GetProcessImageFileName
17-02-2023 17:45:09.407> GetProcessName result 1 time 0ms
17-02-2023 17:45:09.407> FindAppSettings: Matching profile not found.
17-02-2023 17:45:09.407> TimerThread[0xCE0]: Started MOUSE OVER timer 1015 for 150ms - ID 00005580
17-02-2023 17:45:09.560> ProcessMouseOverTimerProc: Checking MouseOver(1543,1652)...
17-02-2023 17:45:09.645> MouseHookLLProc: MouseHookData: Msg=0x0201 (WM_LBUTTONDOWN), X=1543, Y=1652, Data=0x00000000, Flags=0x00000000, Time=3018250, Info=0x0, Ptr=0x60269, Layer=0
17-02-2023 17:45:09.645> Translating Left Button Down Key state 0x0: Action 40 [** No Change (Don't intercept) **]
17-02-2023 17:45:09.645> MouseHookLLProc: Passing original mouse message 0x00000201 through....
17-02-2023 17:45:09.829> MouseHookLLProc: MouseHookData: Msg=0x0202 (WM_LBUTTONUP), X=1543, Y=1652, Data=0x00000000, Flags=0x00000000, Time=3018437, Info=0x0, Ptr=0x60269, Layer=0
17-02-2023 17:45:09.829> Translating Left Button Up Key state 0x1: Action 40 [** No Change (Don't intercept) **]
17-02-2023 17:45:09.829> MouseHookLLProc: Passing original mouse message 0x00000202 through....
17-02-2023 17:45:09.829> TimerThread[0xCE0]: Started MOUSE OVER timer 1015 for 300ms - ID 0000557C
17-02-2023 17:45:10.138> ProcessMouseOverTimerProc: Checking MouseOver(1543,1652)...
17-02-2023 17:45:10.693> MouseHookLLProc: MouseHookData: Msg=0x020b (WM_XBUTTONDOWN), X=1543, Y=1652, Data=0x00020000, Flags=0x00000000, Time=3019296, Info=0x0, Ptr=0x60269, Layer=0
17-02-2023 17:45:10.693> Translating XRight Button Down Key state 0x0: Action 3 [Back]
17-02-2023 17:45:10.693> MouseHookLLProc: Removing message 0x020B (1543,1652) from mouse hook queue as we have overridden it.
17-02-2023 17:45:10.811> MouseHookLLProc: MouseHookData: Msg=0x020c (WM_XBUTTONUP), X=1543, Y=1652, Data=0x00020000, Flags=0x00000000, Time=3019421, Info=0x0, Ptr=0x60269, Layer=0
17-02-2023 17:45:10.811> Translating XRight Button Up Key state 0x0: Action 3 [Back]
17-02-2023 17:45:10.811> Posting APPCOMMAND 0x10000 message to window 00010D7C
17-02-2023 17:45:10.811> MouseHookLLProc: Removing message 0x020C (1543,1652) from mouse hook queue as we have overridden it.

17-02-2023 17:45:15.599> TimerThread[0xCE0]: Started MOUSE OVER timer 1015 for 150ms - ID 0000555C
17-02-2023 17:45:15.747> ProcessMouseOverTimerProc: Checking MouseOver(4223,1485)...
17-02-2023 17:45:15.747> GetProcessIntegrityLevel for PID 14448 returned 0x00001000
17-02-2023 17:45:15.747> GetProcessName(7 WindowFromHWND): Got name for PID 14448, 'firefox.exe' for HWND 0x00030D44 using GetProcessImageFileName
17-02-2023 17:45:15.747> GetProcessName result 1 time 0ms
17-02-2023 17:45:15.747> FindAppSettings: Matching profile not found.
17-02-2023 17:45:15.777> TimerThread[0xCE0]: Started MOUSE OVER timer 1015 for 150ms - ID 0000555A
17-02-2023 17:45:15.926> ProcessMouseOverTimerProc: Checking MouseOver(4148,1463)...
17-02-2023 17:45:16.211> MouseHookLLProc: MouseHookData: Msg=0x0201 (WM_LBUTTONDOWN), X=4148, Y=1463, Data=0x00000000, Flags=0x00000000, Time=3024812, Info=0x0, Ptr=0x60269, Layer=0
17-02-2023 17:45:16.211> Translating Left Button Down Key state 0x0: Action 40 [** No Change (Don't intercept) **]
17-02-2023 17:45:16.211> MouseHookLLProc: Passing original mouse message 0x00000201 through....
17-02-2023 17:45:16.419> MouseHookLLProc: MouseHookData: Msg=0x0202 (WM_LBUTTONUP), X=4148, Y=1462, Data=0x00000000, Flags=0x00000000, Time=3025015, Info=0x0, Ptr=0x60269, Layer=0
17-02-2023 17:45:16.419> Translating Left Button Up Key state 0x1: Action 40 [** No Change (Don't intercept) **]
17-02-2023 17:45:16.419> MouseHookLLProc: Passing original mouse message 0x00000202 through....
17-02-2023 17:45:16.419> TimerThread[0xCE0]: Started MOUSE OVER timer 1015 for 300ms - ID 00005554
17-02-2023 17:45:16.731> ProcessMouseOverTimerProc: Checking MouseOver(4148,1462)...
17-02-2023 17:45:17.691> MouseHookLLProc: MouseHookData: Msg=0x020b (WM_XBUTTONDOWN), X=4148, Y=1462, Data=0x00020000, Flags=0x00000000, Time=3026296, Info=0x0, Ptr=0x60269, Layer=0
17-02-2023 17:45:17.691> Translating XRight Button Down Key state 0x0: Action 3 [Back]
17-02-2023 17:45:17.691> MouseHookLLProc: Removing message 0x020B (4148,1462) from mouse hook queue as we have overridden it.
17-02-2023 17:45:17.997> MouseHookLLProc: MouseHookData: Msg=0x020c (WM_XBUTTONUP), X=4148, Y=1462, Data=0x00020000, Flags=0x00000000, Time=3026593, Info=0x0, Ptr=0x60269, Layer=0
17-02-2023 17:45:17.997> Translating XRight Button Up Key state 0x0: Action 3 [Back]
17-02-2023 17:45:17.997> Posting APPCOMMAND 0x10000 message to window 00030D44
17-02-2023 17:45:17.997> MouseHookLLProc: Removing message 0x020C (4148,1462) from mouse hook queue as we have overridden it.

[phil]

Hi, No this is absolutely nothing to do with the scrolling bug. This is something else - firefox seems to be ignoring the keys sent to it through SendInput (Microsoft's API).

No idea why that would be the case, but it does appear to be a new issue in Firefox 110. Other browsers and older firefox are just fine.
I'm not sure there will be anything I can do about that - this one may be on the Firefox team (I may have to ask them) but I will do a little more digging first.

EDIT: PowerToys keyboard manager can remap keys to browser_back and browser_forward - and it works still in firefox 110, so it probably is a problem in XMBC.. .Just need to figure out where!

EDIT2: Aha... Simulated Keystrokes {BACK} works - does exactly the same as powertoys. Its just the "Browser Back" etc from the dropdown that does not work... I will fix it by doing it the was simulated keystrokes does it!

EDIT3: Thanks - all fixed in 2.20 Beta 13... Well spotted! (And it did turn out to be related to the same root cause in firefox as the scrolling issue - but a completely different code path and solution!)

[phil]

I've just made 2.20 Beta 13 available

The things changed in 2.20 Beta 13 are:

• #782 - Fixed Browser command button remaps (BACK/FORWARD/HOME/REFRESH/STOP/FAVOURITES) not working in Firefox 110.
• #777 - Fixed bug in [Drag to size window] which should only work with sizable windows!
• #775 - Fixed an small/minor issue with the previous change

Feedback welcome. If you think I have missed something you are waiting for, let me know. My full (readonly) todo/bug list is available here.

As usual, any problems, PM me a copy of the log file (or post a snippet in a code block here).

Please keep this beta thread on topic. It is for announcements and reporting bugs in the current beta, NOT for requesting new features and/or asking about existing (non-beta) functionality!

If you have check for beta versions enabled, you should get notified of a new version and prompted to update in the next day or so. This is the most efficient method (bandwidth wise) as the updates are only a fraction of the size of the full install. Otherwise, you can get the full installation beta HERE. Note that this link will always get you the latest beta version!

Regards,
Phil

[phil]

FYI, I Just noticed, if you remap a button to mouse wheel up/down or scroll window up/down in Firefox, it still does not work...

[phil]

I've just made 2.20 Beta 14 available

The things changed in 2.20 Beta 14 are:

• #783 - Fixed remapped actions "Scroll up/down/left/right" and Advanced scrolling do not work in Firefox 110

Feedback welcome. If you think I have missed something you are waiting for, let me know. My full (readonly) todo/bug list is available here.

As usual, any problems, PM me a copy of the log file (or post a snippet in a code block here).

Please keep this beta thread on topic. It is for announcements and reporting bugs in the current beta, NOT for requesting new features and/or asking about existing (non-beta) functionality!

If you have check for beta versions enabled, you should get notified of a new version and prompted to update in the next day or so. This is the most efficient method (bandwidth wise) as the updates are only a fraction of the size of the full install. Otherwise, you can get the full installation beta HERE. Note that this link will always get you the latest beta version!

Regards,
Phil

[Darktemp]

Wow, that was fast!
The back-key works for me now
Thanks a lot!
Still strange, that Firefox changes stuff which was working for 5+ years^^

[phil]

Good good... Had to be fast because I wanted to release 2.20 this weekend (tomorrow with a bit of luck). I'm just glad you found this one before release, and also glad I found the other remapped scrolling problem...

Firefox has made changes to the way tabs are rendered using the GPU I think and isolated from other tabs, so if one crashes, it doesn't take down the whole browser etc. Chrome and Edge have done this for some time now. Its about time Firefox caught up, and in doing so, it caused a few minor problem such as these. The good thing is that they found some of the problems in beta testing and actually got in touch. If I had been a bit quicker, I may have got 2.20 out before Firefox 110, but I would have missed the case you found and the one I found today probably.

Some of these "new" issues were problems in Chrome/Edge etc when they first implemented them, and have had workarounds built into XMBC for several years now!).

EDIT: Thanks for the donation!

[Darktemp]

I'm glad, I could help^^
Although I don't think many poeple remap the back-button

[Laki123]

I installed the new 2.20 version. When I try to change the layer from the context menu, nothing happens. The default layer remains selected.

[phil]

Wow... I haven't even finished publishing it yet (nor updated all the download links)
Let me look into that quickly now...
Hummmm it seemed to work here at first, until I tried selecting a layer with a name... How on earth did that not get picked up in the betas... And out of interest, how did you know 2.20 was "available" before I published any links here - was it just chance??!

EDIT: Can you please download 2.20 again, I have fixed it (and as I hadn't put the release notice out yet, I have just replaced the binaries).

[Laki123]

And out of interest, how did you know 2.20 was "available" before I published any links here - was it just chance??!

EDIT: Can you please download 2.20 again, I have fixed it (and as I hadn't put the release notice out yet, I have just replaced the binaries).

Today I went to the download page and downloaded the latest version 2.20. When I tried to check the latest version from the applications about menu, it reported that I already use the latest version (2.19.2). I was a little confused, but eventually, I downloaded a new version from the website

I downloaded the fixed version 2.20, now it's working as expected. Thanks for a really quick update.

[phil]

OK - just pure chance then that you hit the download page between me updating the URL links, but before I had updated the version number that is queried to check for new versions .

Glad its working now - and thanks for reporting it so promptly!

It looks like there were potentially 120 others who were a little too quick and got the bad 2.20 - we shall see.
I fully expect to be releasing 2.20.1 soon anyway because no doubt there will be other things missed in beta testing, that will get picked up by the wider audience!