http://bugs.winehq.org/show_bug.cgi?id=19667
Summary: Demo for Total Annihilation: mouse scrolling of screen unworkable. Product: Wine Version: 1.1.27 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: hughperkins@gmail.com
Demo for Total Annihilation: mouse scrolling of screen unworkable.
On screens that cannot run at 640x480 resolution, the demo of Total Annihilation has to run in a virtual desktop in order to run at all, otherwise it crashes. This is not I feel the bug.
The issue targeted by this bug report is that it is unworkably hard to scroll around the game world by moving the mouse pointer to the edges of the window, since the mouse pointer has to be positioned *exactly* on the edge of the window, which is possible, but detracts from the gameplay experience to the point as to be unplayable.
A possible solution to this issue (which is not really a bug, so much as a lack of a feature I feel), could be to make it possible to enforce in wincfg that the mouse is locked to a particular region of the window or screen, by default to the window itself.
wincfg could provide the possibility to specify a keyboard shortcut to unlock the mouse when necessary, or simply, by alt-tabbing out of the window, the mouse could be unlocked.
For an example of another environment that implements this, you could look for example at dosbox. If you run for example populous in dosbox in a window, it works perfectly I feel, by locking the mouse pointer to the window, and one can use ctrl-f10 to free it, which I feel is totally unintuitive, but I feel works fine.
http://bugs.winehq.org/show_bug.cgi?id=19667
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|blocker |minor
--- Comment #1 from Dmitry Timoshkov dmitry@codeweavers.com 2009-08-09 23:27:29 --- http://bugs.winehq.org/page.cgi?id=fields.html#bug_severity
http://bugs.winehq.org/show_bug.cgi?id=19667
--- Comment #2 from Hugh Perkins hughperkins@gmail.com 2009-08-09 23:35:16 --- Fine ;-) Btw, somehow the version was set to '0.9'. I've corrected it to 1.1.27.
http://bugs.winehq.org/show_bug.cgi?id=19667
Benjamin Debski benjamin.debski@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |benjamin.debski@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=19667
Benjamin Debski benjamin.debski@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|benjamin.debski@gmail.com |
http://bugs.winehq.org/show_bug.cgi?id=19667
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #3 from joaopa jeremielapuree@yahoo.fr 2011-07-14 01:50:28 CDT --- still a bug in current wine?
http://bugs.winehq.org/show_bug.cgi?id=19667
--- Comment #4 from Austin English austinenglish@gmail.com 2013-11-13 16:51:11 CST --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.6 or newer) wine? If so, please attach the terminal output in 1.7.6 (see http://wiki.winehq.org/FAQ#get_log).
http://bugs.winehq.org/show_bug.cgi?id=19667
Maik Wagner maiktapwagner@aol.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |maiktapwagner@aol.com
--- Comment #5 from Maik Wagner maiktapwagner@aol.com --- Created attachment 49212 --> http://bugs.winehq.org/attachment.cgi?id=49212 Backtrace on wine 1.7.23
I tried the demo from the following address with latest wine. Unfortunately it still crashes. (Backtrace attached)
https://archive.org/details/TotalAnnihilation_201405
http://bugs.winehq.org/show_bug.cgi?id=19667
hanska2@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hanska2@luukku.com
--- Comment #6 from hanska2@luukku.com --- I am not sure of this because I don't understand those backtraces, but I think the crash happens in graphic card driver.
https://bugs.winehq.org/show_bug.cgi?id=19667
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man@post.com
--- Comment #7 from super_man@post.com --- The screen remains black without any patches.
But merging a patch from here
https://bugs.winehq.org/show_bug.cgi?id=35718#c61
get its going. The patch don't apply cleanly anymore but it was enough to get this started.
I didnt use virtual desktop.
I dont see scrolling issue.
wine 1.7.49
https://bugs.winehq.org/show_bug.cgi?id=19667
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #8 from super_man@post.com --- (In reply to Maik Wagner from comment #5)
Created attachment 49212 [details] Backtrace on wine 1.7.23
I tried the demo from the following address with latest wine. Unfortunately it still crashes. (Backtrace attached)
=>0 0x7d876489 in i915_dri.so (+0x29c489) (0x7cee82e8)
It's your gpu for sure.
https://bugs.winehq.org/show_bug.cgi?id=19667
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |https://archive.org/details | |/TotalAnnihilation_201405
--- Comment #9 from Bruno Jesus 00cpxxx@gmail.com --- (In reply to Hugh Perkins from comment #0)
... The issue targeted by this bug report is that it is unworkably hard to scroll around the game world by moving the mouse pointer to the edges of the window, since the mouse pointer has to be positioned *exactly* on the edge of the window, which is possible, but detracts from the gameplay experience to the point as to be unplayable.
A possible solution to this issue (which is not really a bug, so much as a lack of a feature I feel), could be to make it possible to enforce in wincfg that the mouse is locked to a particular region of the window or screen, by default to the window itself.
I'm not sure if this has ever been a bug. At least it looks like wine 1.1.27 already had the option to grab the mouse, and that works for virtual desktops too.
I tried looking for when this feature was introduced but could not find.
https://bugs.winehq.org/show_bug.cgi?id=19667
--- Comment #10 from joaopa jeremielapuree@yahoo.fr --- Scrolling is smooth and very easy in wine-4.18. Can an administrator close this bug as FIXED?
https://bugs.winehq.org/show_bug.cgi?id=19667
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #11 from Jeff Zaroyko jeffz@jeffz.name --- Reported fixed.
https://bugs.winehq.org/show_bug.cgi?id=19667
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 4.20.
-
wine-bugs＠winehq.org -
WineHQ Bugzilla