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

Re: Fix dsiplay of fonts with Symbol codepages (codepage 42) as well

by Dmitry Timoshkov

"David Moore" <davidm(a)sjsoft.com> wrote: > I will change the patch to only CP_UTF7, CP_UTF8 and CP_SYMBOL if you > still suggest I do - this solves my problem. I just thought that my > patch as currently stands (and more so with the addition of CP_UTF8) is > more correct. Please advise. Wine doesn't support those code pages anyway (as yet), so the 3 above should be enough for now. -- Dmitry.

Dec. 15, 2005

Re: Create new mailing list wine-isv?

by Dan Kegel

On 12/15/05, Brian Vincent <brian.vincent(a)gmail.com> wrote: > You're secretly just trying to get me to finish the commercial page I > promised, huh? :-) > I'll vote against a wine-isv list. History has shown we're not > responsible enough to have many mailing lists. Sure, if it takes > off.. great. But more than likely we'll be having a discussion on > wine-devel in 18 months about getting rid of the list because only a > handful of people are subscribed. In the mean time, the 3 or 4 people > who ask questions on wine-isv will get incomplete answers or referred > to wine-devel. Let's have the documentation refer the users to > wine-devel with questions. If things get off topic or wine-devel gets > overwhelmed, then make the list. I would totally agree with you except for one thing: ISVs who are looking at the mailing list archives are going to be overwhelmed by the volume and technical level on wine-devel, and will be afraid to join and post. If everyone agrees that's not really a problem, then I'm fine with directing ISVs to wine-devel. >> [ http://kegel.com/wine/isv/ ] > The stuff you put together looks really nice. Thanks! > There's parts that > could be expanded; the getting started section is easily 20 pages of > written material. Anyway, I think this stuff belongs in the Winelib > User's Guide in some form. Said a different way, I think the Winelib > User's Guide needs to include a section about "Why It's Okay to Ship a > PE Executable". Then again, we all know the Winelib guide needs to be > rewritten. I really don't think Winelib should be involved for the majority of ISVs. Rather than add a section to the Winelib user's guide, let's move all the ISV-oriented stuff to an ISV guide, and add a section in there called "When to use Winelib" that links to the Winelib user guide, or something like that. As with my QA page, I'm happy to help move my ISV page into the official WineHQ doc when it's more ready, but while I'm working on it I prefer to keep using plain HTML on my site. - Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv

Dec. 15, 2005

Re: Create new mailing list wine-isv?

by Brian Vincent

You're secretly just trying to get me to finish the commercial page I promised, huh? I'll vote against a wine-isv list. History has shown we're not responsible enough to have many mailing lists. Sure, if it takes off.. great. But more than likely we'll be having a discussion on wine-devel in 18 months about getting rid of the list because only a handful of people are subscribed. In the mean time, the 3 or 4 people who ask questions on wine-isv will get incomplete answers or referred to wine-devel. Let's have the documentation refer the users to wine-devel with questions. If things get off topic or wine-devel gets overwhelmed, then make the list. The stuff you put together looks really nice. There's parts that could be expanded; the getting started section is easily 20 pages of written material. Anyway, I think this stuff belongs in the Winelib User's Guide in some form. Said a different way, I think the Winelib User's Guide needs to include a section about "Why It's Okay to Ship a PE Executable". Then again, we all know the Winelib guide needs to be rewritten. -Brian

Dec. 15, 2005

Re: Regression in Wine on FreeBSD (DVD Shrink)

by Robert Shearman

Travis Poppe wrote: >Hello All, > >Lately I've been trying to track down a problem that prevents DVD Shrink 3.2 >from starting on FreeBSD in any version of Wine built on/after 04-20-2005 >(including the recent beta releases). Any version built prior to this works >fine. > >I've tracked the problem down to the changes made to x11drv/dib.c (and >associated) on 04-20-2005. I'm not fluent in C; I merely found the problem >through trial and error. > >I have already contacted the author of the changes (dib.c and associated) and >he suggested I try this list. If anyone would like to glance at the >differences between the two files I've mentioned above, I have posted a diff >here: > >http://lickwid.net/~tlp/dib.c.diff > > It's possible that on FreeBSD the signal -> exception translation code doesn't mark whether it was a read or write fault. Other than that, the code should behave the same as before. BTW, you don't need to host the file on a server. People are more likely to look at it if you attach it to your message. -- Rob Shearman

Dec. 15, 2005

Re: Create new mailing list wine-isv?

by David Gümbel

On Mittwoch 14 Dezember 2005 07:33, Dan Kegel wrote: > How about we create a new mailing list, wine-isv, aimed squarely > at ISVs and the Wine community members who want to > help them? Sounds like a good idea to me ;) David

Dec. 15, 2005

Re: fixme:font:load_VDMX Failed to retrieve vTable

by Curro Amores

hi , sorry but im a bit desperated, i dont find the way of sorting out my problem. i send a snapshot of my report so you could give me a hint of what is going wrong, It's a access 97 app and i can not display reports correctly. ill be very pleased. The problem is that i dont get any error with WINEDBG

Dec. 15, 2005

Re: There is no need to offset the source rectangle in the reversedirection before scrolling

by Rein Klazes

On Wed, 14 Dec 2005 22:42:28 +0800, you wrote: >Well, the committed patch 1) does fix a visual glitch in the app I'm working on >and 2) passes all the current tests. 1) You know that doesn't make it right. I see it causing visual glitches in *three* programs here, girotel, native hh.exe and wine's built-in notepad, which does not make it wrong either 2) Indeed, you managed to break functionality that never broke before. > >There are a couple of problems with your tests and fixes It shows a problem. If you could create a test, or otherwise point to a way to reproduce your problem I would not be arguing but looking for a way to fix them all. >: it tests >child windows with CS_PARENTDC style set, and it doesn't test the case >when clipping rect is NULL. In my case both cases are not fulfilled and >therefore we see different results. I still feel you do not understand what you 'fixed': - clipping is plain MSDN specified functionality. Any undocumented restrictions of the dc to a CS_PARENTDC inhered one is unlikely; - if the *special* case cliprect==NULL is not handled correctly, then the correct fix is unlikely to be not to clip in *all* cases. Rein.

Dec. 15, 2005

Re: Create new mailing list wine-isv?

by Stefan Dösinger

Hi, > How about we create a new mailing list, wine-isv, aimed squarely > at ISVs and the Wine community members who want to > help them? I'd say go for it! Stefan

Dec. 15, 2005

Re: [mscms/tests/profile.c] Add another possible error

by Saulius Krasuckas

* On Wed, 14 Dec 2005, Paul Vriens wrote: > > GetStandardColorSpaceProfileW with a non-NULL machinename will return > ERROR_NOT_SUPPORTED on 2000/WinXP/2003 (and maybe more). > > --- a/dlls/mscms/tests/profile.c > +++ b/dlls/mscms/tests/profile.c > @@ -515,7 +515,7 @@ static void test_GetStandardColorSpacePr > /* Parameter checks */ > > todo_wine > - fail_GSCSPW(machineW, 0, newprofile, &size, 0, (GLE == ERROR_INVALID_PARAMETER)); > + fail_GSCSPW(machineW, 0, newprofile, &size, 0, (GLE == ERROR_INVALID_PARAMETER || GLE == ERROR_NOT_SUPPORTED)); Hm, while I believe you, Paul, I don't like testing of several invalid parameters in one check. If different versions of mscms.dll are coded in different ways, we'll be getting one GLE on one platforms and another GLE on anothers. IMHO this way we can test algorithmic (conditional) branching of GetStandardColorSpaceProfile(), which won't be the same on all platforms. So I offer to skip it and test only single parameter in one check. I'll try to send a patch.

Dec. 15, 2005

Re: sysparams : nonclient metric fixes

by Alexandre Julliard

Rein Klazes <wijn(a)wanadoo.nl> writes: > Changelog: > dlls/user : sysparams.c > dlls/user/tests : sysparams.c > Implement saving and fix reading of nonclient metrics with conformance > tests. The test fails here: sysparams.c:195: Test failed: Wrong action got 42 expected 47 -- Alexandre Julliard julliard(a)winehq.org

Dec. 15, 2005