https://bugs.winehq.org/show_bug.cgi?id=50982
Bug ID: 50982 Summary: Mouse clicks are sometimes offset higher (~20 px) than the mouse cursor in LTSpice, winecfg and explorer Product: Wine Version: 6.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: giradischi0001@gmail.com Distribution: ---
Created attachment 69813 --> https://bugs.winehq.org/attachment.cgi?id=69813 winecfg output during prefix creation and automatic wine-mono download
Mouse interactions are sometimes offset 10~30 (random) pixels up from where the cursor is displayed Tried in LTSpice XVII and in winecfg, with wine 6.6 (Arch Linux "wine" package, wine-mono downloaded by wine and not from the Arch package) in a new win64 Windows 7 prefix. Wine 6.5 worked fine. I cannot test with the latest developement version for disk space and available time problems.
## LTSpice XVII LTSpice is a light and easy-to-use electronic simulation freeware by Analog Devices: https://ltspice.analog.com/software/LTspiceXVII.exe (Installation log attached, using app defaults) (Run log attached)
In the component selector: open an existing schematic and right click on a transistor, or create a new schematic and add a transistor (F2, select "npn", Enter, place it anywhere with a left click, then Escape) and right click on it, try to click on new transistor, try to select any of the parts. In the component selection window, in the Bipolar Transistor right-click menu, in the transistor selection dialog and also in the save modified file prompt when exiting, I need to point a bit under the button or item (0~30 pixels, variable) to actually click on the item and not on whatever is immediately over it. Sometimes the offset varies in the same window, for example from about 20 pixels to zero. I did not find that the toolbar, the menu bar or the schematic view were affected. The list of transistor types in the transistor selection dialog also has another problem: the grey header of the list, with labels such as "Part No.", "Manufacturer", Polarity", "Vceo[V]", is often drawn blank or with an incoherent line of the list, and reappears only when scrolling right. This is mentioned to ease usage of the application, ideally I should file another bug for this issue, but I haven't done it in the past three years.
## winecfg While creating the clean prefix (by running winecfg, see also attached log), I found that mouse clicks are also offset in winecfg, for example when adding a drive unit (pointing to a folder), the drop-down menu that allows one to select a drive unit also rolls down only if I click about 20 pixels under its lower margin, and the same for the OK and Cancel buttons. The Add button and the other controls in the winecfg tab do not behave offset.
## explorer The file properties popup has the same offset problem.
It seems to me that the issue manifests itself in popups. Performing enough clicks and resizes on the window, sometimes the offset goes away.
https://bugs.winehq.org/show_bug.cgi?id=50982
Lorenzo Chiola giradischi0001@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux
https://bugs.winehq.org/show_bug.cgi?id=50982
Lorenzo Chiola giradischi0001@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |giradischi0001@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=50982
--- Comment #1 from Lorenzo Chiola giradischi0001@gmail.com --- Created attachment 69814 --> https://bugs.winehq.org/attachment.cgi?id=69814 LTSpiceXVII.exe installer log
https://bugs.winehq.org/show_bug.cgi?id=50982
--- Comment #2 from Lorenzo Chiola giradischi0001@gmail.com --- Created attachment 69815 --> https://bugs.winehq.org/attachment.cgi?id=69815 LTSpice (XVIIx64.exe) run log
https://bugs.winehq.org/show_bug.cgi?id=50982
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon@codeweavers.com
--- Comment #3 from Rémi Bernon rbernon@codeweavers.com --- Is this with Wine Staging or upstream Wine? What kind of desktop environment are you using (window manager more specifically)?
https://bugs.winehq.org/show_bug.cgi?id=50982
--- Comment #4 from Rémi Bernon rbernon@codeweavers.com --- I'm also interested to know whether this is using X11 or XWayland, and if it depends on winecfg Graphics settings (Emulate a virtual desktop, Allow window manager decorations / control).
https://bugs.winehq.org/show_bug.cgi?id=50982
--- Comment #5 from Lorenzo Chiola giradischi0001@gmail.com --- I have IceWM over X11. The wine package is this one, mainstream. https://archlinux.org/packages/multilib/x86_64/wine/
The problem manifests itself only if "Emulate a virtual desktop" is disabled and "Allow window manager decorations" and "Allow window manager control" are enabled.
Based on your words I tried another window manager (spectrwm) and the issue is not present using that.
https://bugs.winehq.org/show_bug.cgi?id=50982
David Koolhoven spambox1@koolhoven-home.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |spambox1@koolhoven-home.net
--- Comment #6 from David Koolhoven spambox1@koolhoven-home.net --- This is also affecting Star Citizen in window mode. This problem existed with WINE staging also, and likely has something to do with the new root offset based coordinate patches they imported to fix window dragging with some windows applications which self update.
https://bugs.winehq.org/show_bug.cgi?id=50982
--- Comment #7 from David Koolhoven spambox1@koolhoven-home.net --- Moving the window at all instantly fixes the problem for me, so I think it has something to do with the assumed window offset coordinate when it's created.
https://bugs.winehq.org/show_bug.cgi?id=50982
--- Comment #8 from David Koolhoven spambox1@koolhoven-home.net --- I need to confirm it, but I suspect https://source.winehq.org/git/wine.git/commit/5a8bc554ef06c4a21d8b49ea8d9362... was the source of this problem, but this problem seems to be gone with the current nightly build. It might be solved in 6.8.
https://bugs.winehq.org/show_bug.cgi?id=50982
--- Comment #9 from Ken Sharp imwellcushtymelike@gmail.com --- Did you confirm that this is fixed?