January 2005 - Wine-Devel - list.winehq.org

Re: unicode "tables"

by Mike McCormack

Jonathan Wilson wrote: > I remember some people talking about some kind of "unicode tables" that > WINE has but that dont match with the MS implementation. > What are the tables for? > And what API call(s) are involved? StringCompareA/W and related functions won't do the exactly the same thing as Windows, as Wine uses standard Unicode collation tables. Mike

Jan. 28, 2005

unicode "tables"

by Jonathan Wilson

I remember some people talking about some kind of "unicode tables" that WINE has but that dont match with the MS implementation. What are the tables for? And what API call(s) are involved?

Jan. 28, 2005

Re: [WINETEST] How is a visible desktop detected

by Ferenc Wagner

Paul Vriens <Paul.Vriens(a)xs4all.nl> writes: > I have a Win98/WNT/W2K (on VMWare) and a XP Home > system. All are running the winrash service. All were > started when I was logged in but only the W98 and WNT were > considered running on a visible desktop. Hmm, services use an invisible desktop by default AFAIK. It shouldn't matter how you started winrash (the service), but how you started winetest itself. If it's started by winrash, it runs on an invisible desktop; if you start it, it runs on a visible desktop. It's either buggy or misnamed, reality suggests. It was invented to account for metafile test failures, which require a visible desktop, see eg. http://test.winehq.org/data/200501271000/nt4_IvanLeo/gdi32:metafile.txt Now it looks it depends on something else instead, and you are in a pretty good position to find out what! I haven't got a clue, including this flag was suggested by others. > What's the criteria for 'running on a visible desktop'? programs/winetest/main.c (as offered by Dmitry Timoshkov): static int running_on_visible_desktop () { return (GetWindowLongA (GetDesktopWindow (), GWL_STYLE) & WS_VISIBLE != 0); } -- Feri.

Jan. 28, 2005

Re: MSVCRT: Re-implement *printf

by Aneurin Price

Changelog: > Re-implement all *printf functions in msvcrt.dll, according to > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html… > > and descriptions of appropriate functions. > This should fix, among other things, bugs 321 and 2075. > Nobody has any comments about this?

Jan. 28, 2005

Re: X11DRV: Fix to incorrect detection and other bugs of keyboard driver in XKB presence

by Alexandre Julliard

"Oleh R. Nykyforchyn" <nick(a)pu.if.ua> writes: > Add alternative (alpha) code to keyboard driver in x11drv that can handle > correct detection and switching of keyboard layout both with and without > XKB extension. Add temporary --enable-xkb feature to configure script > to enable compilation with new code instead of existing one. You really need to get rid of these #ifdefs. If the patch is not working well enough to be enabled by default it won't go in at all. Most likely you need to split it in smaller parts that can be tested and applied separately. -- Alexandre Julliard julliard(a)winehq.org

Jan. 28, 2005

Re: msvcrt: translate name to locate program

by Alexandre Julliard

Michael Wu <flamingice(a)sourmilk.net> writes: > Would passing an empty path (eg. ".") to the function solve the problem? > SearchPath does a lot of what spawn needs to find the real filename, and I'd > like to avoid duplicating what SearchPath does. If all you need is to append ".exe" calling SearchPath doesn't seem necessary at all. -- Alexandre Julliard julliard(a)winehq.org

Jan. 28, 2005

Re: Re: [winecfg] Show detected audio systems, and offer selection

by Paul van Schayck

So in the end we will just keep it all the same for now? Or did I lost you all. Or do we want to follow Chris suggestion by offering a frontend to the driver load order list? Thanks, Paul

Jan. 28, 2005

Re: [Fwd: Wine-Wiki.org]

by Stefan Munz

Am Donnerstag, 27. Januar 2005 10:30 schrieb Jonathan Ernst: <big snip> > > > > So these 'supported' applications are no different from any other > > application and the medals mean nothing more than the old rating system. > > They just have 4 levels instead of 6. > > I think having more than 3-4 levels is too much by the way; it's much > too hard to rate an application in such small quality steps. maybe it is a good idea to seperate the installation rating from how well the program runs. I often had problems to install apps that run perfectly if you get past the installer ;-). just my 2 cents ... > > As for application that could regress from gold to another rating, I > think that's not a problem as when a maintainer rates an application he > states what version of Wine he was using (next drop down box after the > maintainer rating). > > I even started to track an history of application ratings for the apps I > maintain: each time I retest an application I update the application > rating AND the history table so that someone can figure out that an > application was working better with an older wine release. > > See here for examples: > http://appdb.winehq.org/appview.php?appId=1533&versionId=2230 > http://appdb.winehq.org/appview.php?appId=2&versionId=764 that's a very good idea and i think the rating system in general should be linked to a wine version otherwise it's relatively useless. I always read the comments to figure out wether the (hopefully good ;-) rating of an app maybe is based on a wine version from 2001. cu, Stefan

Jan. 28, 2005

Re: [Fwd: Wine-Wiki.org]

by Francois Gouget

On Thu, 27 Jan 2005 tony_lambregts(a)telusplanet.net wrote: > Francois Gouget wrote: > [Snip] >> >> * Test the application on a regular basis. >> >> Ideally you would test it once a week so that you can quickly notify the >> Wine developers of any regression. The earlier a Wine regression is >> noticed, the easier it will be to locate the change that causing it and the >> more likely it is to be fixed. >> At the very least you should test the application with each Wine >> release. If you detect a regression at that point it is likely you will >> have to go through regression testing to identify the patch causing the >> problem. >> Also mention any stability problem. > > I thought I was :-) No, I'm not talking about your concept of stability here. Maybe you realised that but just in case to make things clear, here I'm asking the maintainer to mention in his report whether the application tends to crash or freeze seemingly randomly (if it's a specific action that causes trouble it would go in the list of things that don't work). > So instead of answering the question you avoid the question entirly. Wine's release cycle is simply irrelevant to the Application Maintainer's Guide. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ $live{free} || die "";

Jan. 28, 2005

Re: [x11/keyboard] numpad 5 key

by Dmitry Timoshkov

"Oliver Stieber" <oliver_stieber(a)yahoo.co.uk> wrote: > This little patch sends a scancode through for the 5 > key when numlock isn't on. > > This is needed to fire cannons in pirates. > > I hope this is ok, a quick test showed that the > keydown was already sending a scancode, but it may be > wrong, this just fixes keyup and should be correct. > - VK_END, 0, VK_INSERT, VK_DELETE, > + VK_END, 0x0c, VK_INSERT, VK_DELETE, Running spy++ under Windows confirms that your patch is correct, you just need to use symbolic name VK_CLEAR instead of 0x0c. -- Dmitry.

Jan. 28, 2005