[Bug 56394] New: Final Fantasy XI Online: Mouse/pointer cursor activates at unintended times.
https://bugs.winehq.org/show_bug.cgi?id=56394 Bug ID: 56394 Summary: Final Fantasy XI Online: Mouse/pointer cursor activates at unintended times. Product: Wine Version: 9.0-rc3 Hardware: x86-64 URL: https://web.archive.org/web/20210810150839/http://www. playonline.com/ff11eu/download/media/install_win.html OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chiitoo(a)gentoo.org CC: eric.pouech(a)gmail.com, temp82(a)luukku.com Regression SHA1: 6c11a4af5885c6485a908ea5c547e072fe71aa23 Distribution: Gentoo After d1789fbb40d [1], the pointer cursor in Final Fantasy XI Online (FFXI) may activate when it should not. Perhaps somehow related to how FFXI, when running in fullscreen or a borderless window, can "warp" the cursor to certain locations on the screen when a pointer device is used to open certain menus, so no actual movement of the device is needed when going from a menu to another. Normally the cursor is hidden when using only the keyboard or a gamepad, but due to this issue, the cursor may activate when pressing 'cancel', and due to how log windows may be set up in the game, this can lead into the cursor actually changing the selection in a menu. It is extremely noticeable during battle, when using a gamepad and multiple reactive horizontal log windows, and pressing 'cancel' repeatedly to minimise the log windows. There is something similar that can be made manifest in a native Windows environment as well, but it is slightly different, and a report for a different tracker. Reverting the referenced refactoring restores behaviour to that of the native environment. Thank you! 1. https://source.winehq.org/git/wine.git/commitdiff/d1789fbb40d74b747451c9c5d9... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56394 Chiitoo <chiitoo(a)gentoo.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1|6c11a4af5885c6485a908ea5c54 |d1789fbb40d74b747451c9c5d9e |7e072fe71aa23 |738c463a6aa67 Keywords| |regression -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56394 Chiitoo <chiitoo(a)gentoo.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon(a)codeweavers.com Fixed by SHA1| |994021da996f06f3fd65670b19c | |301ed77441c5c Status|UNCONFIRMED |RESOLVED Component|-unknown |wineserver Resolution|--- |FIXED --- Comment #1 from Chiitoo <chiitoo(a)gentoo.org> --- This seems to have been fixed by 994021da996 [1], and as such, fixed in wine-9.5. It is still possible to trigger sometimes by being very fast with the inputs, or holding ESC and pressing cancel on a gamepad, but that also happens in the native environment. What comes to Wine, though, things do indeed seem to be back to normal. Very many very thanks! 1. https://source.winehq.org/git/wine.git/commitdiff/994021da996f06f3fd65670b19... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56394 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #2 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 9.6. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56394 --- Comment #3 from Chiitoo <chiitoo(a)gentoo.org> --- A bit of a follow-up on this... It seems that the issue is still there, /sometimes/, and I can now see it happening even with the parent commit of the SHA currently marked as the regression introducer. There must be some unknown factor to it all, since when testing this, I could not make it happen while trying for several minutes, several times, and then right away with the mentioned change applied. Will try to dig more into this, as time and energy permits. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla