http://bugs.winehq.org/show_bug.cgi?id=23907
Summary: Winecfg should not allow resolutions lower than X amount Product: Wine Version: unspecified Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: luisalvaradox@gmail.com
I write this because one of my students of Ubuntu just happen to do something that i did not think of. He open winecfg and change the resolution to 10x800. Winecfg allowed him to change to that resolution which created a problem when opening winecfg or any other window without the resolution parameter.
My bug is about limiting the smallest resolution on winecfg. It should be something around 640x480 since that is the lowest VGA. So resolutions lower than 640x480 or maybe something smaller should not be allowed to make it a bit more friendlier to new ubuntu and wine users.
My solucion was to edit the .wine/user.reg file, find the line that points to the 10x800 resolution and change it there but this does not help in making it easier to newcomers. Hope this gets somebody to help with this.
Thank you.
http://bugs.winehq.org/show_bug.cgi?id=23907
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, source Component|-unknown |programs Version|unspecified |1.3.0 Severity|normal |enhancement
http://bugs.winehq.org/show_bug.cgi?id=23907
David aim_here2002@yahoo.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |aim_here2002@yahoo.co.uk
--- Comment #1 from David aim_here2002@yahoo.co.uk 2010-08-05 08:53:11 --- I'm under the impression that 320x200 - the equivalent to DOS VGA mode 0x13 - is more likely to be the lowest VGA mode. Certainly, there are fullscreen Windows apps that use it, such as the Windows ports of the first two Xcom games, so the limit, whatever it is, shouldn't be larger than that.
http://bugs.winehq.org/show_bug.cgi?id=23907
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|All |Other Summary|Winecfg should not allow |Winecfg should not allow |resolutions lower than X |resolutions lower than |amount |640x480 amount
--- Comment #2 from Dmitry Timoshkov dmitry@codeweavers.com 2010-08-05 09:34:45 --- winecfg dialogs are designed for 640x480, so it would be reasonable to have it as the lowest resolution.
http://bugs.winehq.org/show_bug.cgi?id=23907
--- Comment #3 from Luis Alvarado luisalvaradox@gmail.com 2010-08-05 21:39:09 --- Actually i was talking to the minimum size that winecfg can have taking into consideration the minimum resolution a VGA monitor (Those SUPER OLD ONES) have. 0x13 for Dos is something like 320x200 i dont remember correctly but wine is more made for 640x480 apps and up. So it would be better to point it to that. But they point is, it does not matter what resolution the minimum gets at, what it matters is that it does not get so small as to get to stuff like 80x100 or, you guessed it, 1x1. So if the minimum has to be 320 then ok, if it is 640 then ok too but not so small that a newcomer can not do anything after that.
Hope this clarifies why i created the bug report.
http://bugs.winehq.org/show_bug.cgi?id=23907
--- Comment #4 from Dmitry Timoshkov dmitry@codeweavers.com 2010-08-06 01:28:01 --- The new resolution should allow running winecfg, and winecfg should remain usable.
http://bugs.winehq.org/show_bug.cgi?id=23907
--- Comment #5 from Luis Alvarado luisalvaradox@gmail.com 2010-08-06 10:32:03 --- (In reply to comment #4)
The new resolution should allow running winecfg, and winecfg should remain usable.
True
http://bugs.winehq.org/show_bug.cgi?id=23907
--- Comment #6 from Vincent Povirk madewokherd@gmail.com 2010-08-23 17:33:44 --- Apps should still be able to set the resolution of a virtual desktop to a smaller size. This works without changing the configured value, and still leaves winecfg usable.
If an app really needs to be started with the display set to 320x200, I think it's reasonable to have to set that using explorer or regedit.
http://bugs.winehq.org/show_bug.cgi?id=23907
--- Comment #7 from Vincent Povirk madewokherd@gmail.com 2010-08-23 17:48:45 --- Patch sent: http://www.winehq.org/pipermail/wine-patches/2010-August/092446.html
http://bugs.winehq.org/show_bug.cgi?id=23907
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #8 from Austin English austinenglish@gmail.com 2010-08-24 11:18:41 --- (In reply to comment #7)
Patch sent: http://www.winehq.org/pipermail/wine-patches/2010-August/092446.html
Committed: http://source.winehq.org/git/wine.git/?a=commitdiff;h=be1aa20276706f216c7679...
http://bugs.winehq.org/show_bug.cgi?id=23907
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Alexandre Julliard julliard@winehq.org 2010-09-03 14:05:30 CDT --- Closing bugs fixed in 1.3.2.
http://bugs.winehq.org/show_bug.cgi?id=23907
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |1.2.x
http://bugs.winehq.org/show_bug.cgi?id=23907
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|1.2.x |---
--- Comment #10 from Alexandre Julliard julliard@winehq.org 2010-10-08 10:40:16 CDT --- Removing 1.2.x milestone from bugs fixed in 1.2.1.
-
wine-bugs＠winehq.org