Hi Bernhard,

re:
> That why I thought this mechanism might be suitable to determine which view has the focus
> for the mouse-wheel zoom.

I see. But that particular mechanism is part of the operating system - the way Windows is set up a mouse move message is sent to the window the mouse cursor is over (unless the mouse has been captured) while a mouse wheel message is sent to the window that has keyboard focus.

But it should not be difficult for me to cook up something similar.

- Michael

Hi Bernhard, so now that I dig into it a bit more I see that there is already something in place that is supposed to be routing mouse wheels to the viewport under the mouse.

So I guess the MoI function that retrieves the viewport under the mouse cursor point is not working right on your system.

Is your multi monitor configuration unusual in any way, like is each monitor in some separate coordinate space instead of being all one connected desktop or something like that?

- Michael

Hi Michael,

Thanks for your continued support!

My setup might be slightly unusual in two ways:

a) I'm using six 1920x1200 24" displays (3 columns, 2 rows) where the left two displays are directly connected to the video card (as usual) and the other four displays are connected via two "Matrox DualHead2Go Digital SE" to the same video card. Means, the OS detects two 1920x1200 and two 3840x1200 displays (forming a 5760x2400 desktop in total). The Matrox splitters are necessary because the Radeon RX7900XTX can only drive up to four displays. I temporarily disabled the outputs for the two DH2G so that there are only two 1920x1200 displays connected but there is no improvement.

b) The top three displays are operated in "inverted" mode because they are mounted upside down to have a thin bezel between the displays. I temporarily disabled the outputs for the two DH2G so that there are only two 1920x1200 displays connected and operated both displays in "normal" (not inverted) mode but there is no improvement.

BTW.: the same effect is observable for GNOME 44 with X11 and Wayland

I'll temporarily install V4 on a PC that has an nvidia card, just to make sure it's not an issue with the amdgpu driver.

Looking forward to try out the solution :-)

TIA and best regards

Bernhard

Just a quick update concerning the following statement:

> I'll temporarily install V4 on a PC that has an nvidia card, just to make sure it's not an issue with the amdgpu driver.

Unfortunately, the installation of MoI V4 fails: after executing the installer, a window with all black content shows up and the installer hangs.
I also tried installing MoI V3, but the installer hangs right after execution. This is with latest Fedora 38 packages and nvidia driver 535.54.03 (latest production driver).
MoI V3 used to run on that PC, many years back (f23). Probably some kind of regression in Fedora or the nvidia driver.

Hi all!

Just to keep you in the loop:

Michael fixed the mouse wheel zoom autofocus issue for Linux/Wine! Many, many thanks, I highly appreciate it!

Michael wrote that the fix will be included in the next beta release.

He also wrote that if other Linux users are running into the same specific problem (which is with windows extending across multiple monitors running under Wine in Linux) then they can e-mail him to get a patched v4.

best regards

Bernhard