April 2008 - Wine-Devel - list.winehq.org

Re: wine.inf.in: use lowercase for Microsoft Video 1

by Jeff Zaroyko

On Sun, Apr 27, 2008 at 10:22 PM, Dmitry Timoshkov <dmitry(a)codeweavers.com> wrote: > "Jeff Zaroyko" <jeffzaroyko(a)gmail.com> wrote: > > > > system.ini, drivers32,,"vidc.MRLE=msrle32.dll" -system.ini, > drivers32,,"vidc.MSVC=msvidc32.dll" +system.ini, > drivers32,,"vidc.msvc=msvidc32.dll" system.ini, > drivers32,,"vidc.CVID=iccvid.dll" system.ini, drivers32,,"; > vidc.IV50=ir50_32.dll" system.ini, drivers32,,"; vidc.IV31=ir32_32.dll" > > > > MRLE and CVID are also in lower case in XP, so they should be fixed too > (as well as removed trailing spaces in many entries in [SystemIni] > section). > > -- > Dmitry. > If I should make these changes and resubmit, what about MSACM entries? I see that they are also lower case on XP.

April 27, 2008

Re: Dan Kegel : winecfg: Restrict dpi slider to sane values.

by Dmitry Timoshkov

"Tijl Coosemans" <tijl(a)ulyssis.org> wrote: > If users want a graphical way of setting physical display size, then > that's a job for the desktop environments to provide some tools to > configure the local X server. Same applies to many other settings like fonts and colors. Wine uses the DPI setting only as a way to scale fonts, not as a general size scaler. > The only time Wine should have to worry about DPI is when running > apps that haven't been designed with high DPI in mind and therefore > don't scale well (for instance when font sizes are set in points and > other GUI elements are sized or positioned using pixels). But for those > apps it might be good enough to provide a simple checkbox that says > "override DPI to 96" or some other sensible default value. I don't know > if there actually are such apps. Such apps would break in Windows as well, Win32 uses logical units for its GUI elements, not pixels. Besides, even Windows does go that far as forbidding large DPI values, but Windows makes it clear what a user will get using a font preview window. -- Dmitry.

April 27, 2008

Re: Dan Kegel : winecfg: Restrict dpi slider to sane values.

by Tijl Coosemans

> "Dan Kegel" <dank(a)kegel.com> wrote: >> On Sat, Apr 26, 2008 at 7:54 PM, L. Rahyen <research(a)science.su> wrote: >>> 200 DPI limit is acceptable for most users. However, what this patch >>> done by setting maximum to this small value (144) doesn't seems to >>> be acceptable. >> >> Users really are lost if they set a too-high value. >> They don't know how to do alt+mouse_move. >> Thus simply setting the limit higher again would >> be a support nightmare; we got a preview of that >> on wine-users recently, with user after user panicking. >> >> But as I wrote in http://bugs.winehq.org/show_bug.cgi?id=9715 >> we can probably do something that will make everybody >> happy: arrange for winecfg to never let the user set >> dpi so high that winecfg is bigger than the screen. >> That's probably pretty easy to do. >> >> And we can probably make high-res users happier still >> by defaulting to Xft.dpi (used by Gnome and maybe KDE; >> it's set by default to 96, but is increased by some users >> of high-res displays). IMO the Mozilla page you linked to in the bug is the correct approach. Users should set the DisplaySize setting in their X server configuration (if it isn't detected automatically). And applications should (by default) use the X server DPI calculated from that. Applications overriding the X server DPI are bad when you start to run them remotely. If users want a graphical way of setting physical display size, then that's a job for the desktop environments to provide some tools to configure the local X server. The only time Wine should have to worry about DPI is when running apps that haven't been designed with high DPI in mind and therefore don't scale well (for instance when font sizes are set in points and other GUI elements are sized or positioned using pixels). But for those apps it might be good enough to provide a simple checkbox that says "override DPI to 96" or some other sensible default value. I don't know if there actually are such apps.

April 27, 2008

Re: wine.inf.in: use lowercase for Microsoft Video 1

by Dmitry Timoshkov

"Jeff Zaroyko" <jeffzaroyko(a)gmail.com> wrote: > system.ini, drivers32,,"vidc.MRLE=msrle32.dll" > -system.ini, drivers32,,"vidc.MSVC=msvidc32.dll" > +system.ini, drivers32,,"vidc.msvc=msvidc32.dll" > system.ini, drivers32,,"vidc.CVID=iccvid.dll" > system.ini, drivers32,,"; vidc.IV50=ir50_32.dll" > system.ini, drivers32,,"; vidc.IV31=ir32_32.dll" MRLE and CVID are also in lower case in XP, so they should be fixed too (as well as removed trailing spaces in many entries in [SystemIni] section). -- Dmitry.

April 27, 2008

Re: Dan Kegel : winecfg: Restrict dpi slider to sane values.

by Dmitry Timoshkov

"Dan Kegel" <dank(a)kegel.com> wrote: > On Sat, Apr 26, 2008 at 7:54 PM, L. Rahyen <research(a)science.su> wrote: >> 200 DPI limit is acceptable for most users. However, what this patch done by >> setting maximum to this small value (144) doesn't seems to be acceptable. > > Users really are lost if they set a too-high value. > They don't know how to do alt+mouse_move. > Thus simply setting the limit higher again would > be a support nightmare; we got a preview of that > on wine-users recently, with user after user panicking. > > But as I wrote in http://bugs.winehq.org/show_bug.cgi?id=9715 > we can probably do something that will make everybody > happy: arrange for winecfg to never let the user set > dpi so high that winecfg is bigger than the screen. > That's probably pretty easy to do. > > And we can probably make high-res users happier still > by defaulting to Xft.dpi (used by Gnome and maybe KDE; > it's set by default to 96, but is increased by some users > of high-res displays). > > Anyone willing to try implementing that? I'd do it, but I'm kind of > limited by sore hands and time these days... How about doing what Windows does - add a font preview to allow the user to see an actual size of the font he/she will get after the change? -- Dmitry.

April 27, 2008

Re: msvcrt: Remove two tests that fail on all platforms

by Eric Pouech

James Hawkins a écrit : > Hi, > > Changelog > * Remove two tests that fail on all platforms. > > dlls/msvcrt/tests/cpp.c | 2 -- > 1 files changed, 0 insertions(+), 2 deletions(-) > > > ------------------------------------------------------------------------ > > the first one is actually bogus, I'll send a corrected test however, the second seems ok (except some space difference) can you post the failing test information ? A+ -- Eric Pouech "The problem with designing something completely foolproof is to underestimate the ingenuity of a complete idiot." (Douglas Adams)

April 27, 2008

Re: 1.0 idea - ntdll - add a messagebox for missing dlls

by Steven Edwards

On Sat, Apr 26, 2008 at 1:53 PM, Steven Edwards <winehacker(a)gmail.com> wrote: > > * have start.exe set an environment variable saying "show graphical error box > > on dll load failure", and clear that before calling executed apps' WinMain() > > (easy) > > So something like start.exe.so in Unix mode would set a variable like > VERSBOSE_USERDEBUG or which then we could query in the loader using > RtlQueryEnvironmentVariable_U or something that would trigger the > MessageBox from the example code I already wrote in ntdll? So that worked. Comments are welcome! -- Steven Edwards "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo

April 27, 2008

Re: Dan Kegel : winecfg: Restrict dpi slider to sane values.

by L. Rahyen

On Sunday April 27 2008 03:23:40 Dan Kegel wrote: > But as I wrote in http://bugs.winehq.org/show_bug.cgi?id=9715 > we can probably do something that will make everybody > happy: arrange for winecfg to never let the user set > dpi so high that winecfg is bigger than the screen. Yes, I think this would be better solution. This will probably will work well for everyone and will be much better than hard-coded limit.

April 27, 2008

Re: Dan Kegel : winecfg: Restrict dpi slider to sane values.

by Dan Kegel

On Sat, Apr 26, 2008 at 7:54 PM, L. Rahyen <research(a)science.su> wrote: > 200 DPI limit is acceptable for most users. However, what this patch done by > setting maximum to this small value (144) doesn't seems to be acceptable. Users really are lost if they set a too-high value. They don't know how to do alt+mouse_move. Thus simply setting the limit higher again would be a support nightmare; we got a preview of that on wine-users recently, with user after user panicking. But as I wrote in http://bugs.winehq.org/show_bug.cgi?id=9715 we can probably do something that will make everybody happy: arrange for winecfg to never let the user set dpi so high that winecfg is bigger than the screen. That's probably pretty easy to do. And we can probably make high-res users happier still by defaulting to Xft.dpi (used by Gnome and maybe KDE; it's set by default to 96, but is increased by some users of high-res displays). Anyone willing to try implementing that? I'd do it, but I'm kind of limited by sore hands and time these days... - Dan

April 27, 2008

Re: Dan Kegel : winecfg: Restrict dpi slider to sane values.

by L. Rahyen

On Saturday April 26 2008 23:22:37 Dan Kegel wrote: > On Sat, Apr 26, 2008 at 10:40 AM, Lei Zhang <thestig(a)google.com> wrote: > > > > URL: > > > > http://source.winehq.org/git/wine.git/?a=commit;h=faaccca59be08be54 > > > >7ec4e1948b6306eff3808a2 > > > > > > > > Author: Dan Kegel <dank(a)kegel.com> > > > > Date: Tue Apr 22 17:56:36 2008 -0700 > > > > > > > > winecfg: Restrict dpi slider to sane values. > > > > > > Dan, this basically reverted commit > > > 0110512904d9c646abef416819a057c06d3f2c97, which bumped MAXDPI from > > > 160 to 480 because some users specifically requested the ability for > > > higher DPI settings. > > > > > > I think we need to decide what we want and stop the tug-o-war. > > > > Please see bug 9715. > > 480 was completely unusable; average Joes were setting it > at random and were unable to use winecfg to reset it to > something sane. > > I found a few monitors out there at 200 dpi, so perhaps that would > be a reasonable upper limit, but we'd have to check to make sure that > the average person with a crap monitor could set that to 200dpi, > realize it was wrong, > - Dan 200 DPI limit is acceptable for most users. However, what this patch done by setting maximum to this small value (144) doesn't seems to be acceptable. There is enough users who want higher values and BTW I'm one of them (I need 150 and 160; I need two values because I have more than one monitor/computer). So if we want to set the maximum limit lower than on Windows we need to choose reasonable value for most of us. I propose that we agree on at least 200 DPI limit in winecfg otherwise this puts too much inconvenience (especially for everyone who create new WINE prefix for new set of Windows programs, and this is what I do regularly). > and set it back without having to edit the registry by hand. Just a note: in all WMs I have tried winecfg remains usable even on 480 DPI because you can move the window as usually with Alt+Mouse_move or Meta+Mouse_move, and you need to move the window only once to reset the setting to any other value.

April 27, 2008