May 2003 - Wine-Devel - list.winehq.org

Re: Volunteers needed - windows API db script ready

by Gerhard W. Gruber

On Fri, 2 May 2003 01:57:36 -0400 (EDT), Dave Miller <compsol(a)ptdprolog.net> wrote: >The script which dumps dll imports and exports now seems to parse >everything correctly and organize it nicely in a text file. We need the >script run against various windows versions. The output can be sent >directly to me, but please verify I do not already have the data for that >particular version of windows. I don't need 10 copies of win2k SP3 for >example. :) I'm not sure if I understand you script crorrectly. Does the script scan actual DLL binaries for import/export info and converts it to a spec file? Or does this script only take a spec file? -- Gerhard Gruber Für jedes menschliche Problem gibt es immer eine einfache Lösung: Klar, einleuchtend und falsch. (Henry Louis Mencken)

May 2, 2003

Re: Small DSound fix...

by Christian Costa

Lionel Ulmer wrote: >Hi all, > >This makes games which do NOT enumerate the sound devices and go through the >ClassFactory work. > >It has also some miscellaneous tracing fixes. > >Changelog: > - misc. tracing fixes > - handle IID_IDirectSound(8) as the default sound driver > A ce que je vois ton patch remplace le mien (qui n'a pas ete accepte d'ailleurs)... P'tite curiosite.. :-) : Mais qu'est ce que ces foutues IIDs viennent faire a la place des GUID des devices ? C'est une bidouille ou bien DirectSoundCreate les acceptent vraiment ? Christian

May 2, 2003

Re: Small DSound fix...

by Lionel Ulmer

Replying in English :-) > A ce que je vois ton patch remplace le mien (qui n'a pas ete accepte > d'ailleurs)... Did not remember that you submitted a patch for this... Was only aware of the DInput one for ClassFactory, not the one on DSound. > P'tite curiosite.. :-) : > Mais qu'est ce que ces foutues IIDs viennent faire a la place des GUID > des devices ? > C'est une bidouille ou bien DirectSoundCreate les acceptent vraiment ? >From what I know, it's about the same as out 'fake' GUIDs we have for DirectX. Ie each driver has its own GUID so that a game can specifically ask for one device (and when a game asks Wine to enumerate the DSound devices, these 'fake' devices are actually returned => it works fine there). The problem is for games expecting the default driver being returned when using the 'generic' GUID (ie without doing an enumeration and without using the DefaultPlayback GUID). Lionel -- Lionel Ulmer - http://www.bbrox.org/

May 2, 2003

Re: Small DSound fix...

by Vincent Béron

Christian Costa a écrit: > Lionel Ulmer wrote: > >> Hi all, >> >> This makes games which do NOT enumerate the sound devices and go >> through the >> ClassFactory work. >> >> It has also some miscellaneous tracing fixes. >> >> Changelog: >> - misc. tracing fixes >> - handle IID_IDirectSound(8) as the default sound driver >> > > A ce que je vois ton patch remplace le mien (qui n'a pas ete accepte > d'ailleurs)... > > P'tite curiosite.. :-) : > Mais qu'est ce que ces foutues IIDs viennent faire a la place des GUID > des devices ? > C'est une bidouille ou bien DirectSoundCreate les acceptent vraiment ? Envoyé en français par erreur à la liste probablement Christian? :) Whole translation for non-french speaking people here: I see that your patch replaces mine (which hasn't been accepted yet)... Out of curiosity... :-) : What all those bloody IIDs do instead of devices' GUID? Is it a gimmick or does DirectSoundCreate really accepts them? (me) Sent to the list by mistake in French Christian? :) Vincent

May 2, 2003

Re: Assertion `!sem->obj.head' failed in release_semaphore

by Alexandre Julliard

Rein Klazes <rklazes(a)xs4all.nl> writes: > Trying with several old wines, reveals that this bug is at least 3 > months old, apparently not related to the new threading code. > > I've searched through the trace and the server code (it must be a server > bug, doesn't it?) but see nothing obviously wrong. Actually that assert is wrong now that we support nested waits. I have removed it. -- Alexandre Julliard julliard(a)winehq.com

May 2, 2003

Re: Re: Callbacks while app is looping

by Mark Westcott

On Thursday 01 May 2003 10:42 am, Mike Hearn wrote: > > This is as far as I can get (new to wine) - any ideas anyone? I threw a > > test case app that illustrates the problem > > Could you make that available? either C source with Makefile or compiled > EXE is fine. Sure, exe is here: http://www.befishy.co.uk/files/GetDeviceStateTest.exe > > (btw, the WH_KEYBOARD_LL hook has the note 'should use SendMessage > > instead', but I don't get what this means or know if using SendMessage > > instead would have anything to do with fixing this problem) > > It might do, poking around in the windows/input.c file reveals the hook > is called using HOOK_CallHooks() rather than sending a message. MSDN > says Windows internally uses messages to implement this one for some > reason, but on the other hand presumably DirectInput knows how Wine does > it. Ok, but I just did a little bit more poking and it turns out that windows/input.c:queue_kbd_event isn't getting called at all, and back further, nor is SendInput() or kbd_event(). (Btw, mouse events don't get through either during the while (1) loop.), so the fact its calling the hooks this way isn't the problem. > Being able to play with the test app would make it easier to debug this > problem. > > Also, if any Wine/Win32 gurus could point to some docs on how callback > routines are invoked, that'd be useful. > One other possibility is that DirectInput should not be using keyboard > event hooks in this way. GetDeviceState() implies reading the keyboard > device directly, or reading an internal map of key states - NOT waiting > for keyboard events. But, I haven't seen that code and didn't implement > it, so I might be talking rubbish. Well, the wine DInput implentation keeps an internal map of key states and updates these when an event happens. Its just this badly written bit of code thats using it to wait for a keyboard event :) > thanks -mike (TD on irc) Thanks for the response Mike, Mark

May 2, 2003

Re: Re: Callbacks while app is looping

by Mike Hearn

> Well, the wine DInput implentation keeps an internal map of key states and > updates these when an event happens. Its just this badly written bit of code > thats using it to wait for a keyboard event :) I suspect the actual problem is that keyboard hooks require the app to be processing messages in order to function. In fact, run that test app in desktop mode - you'll see that it works fine, presumably because the desktop continues processing messages even when the app within it is not. I'm not sure what to do about this, it'd seem sensible to have X11 events processed by the service thread, but I suspect there are reasons why this isn't the case. CCing Alexandre, he'll know more about hooks/callbacks. thanks -mike

May 2, 2003

Re: Solaris Update Patch 02052003

by Dimitrie O. Paun

On Fri, 2 May 2003, Robert Lunnon wrote: > OOPS forgot to attach the patch here it is This pcontext() thing is very ugly: +static void pcontext ( CONTEXT *context, int trap_code, void *cr2, int err_code){ Please do a const char *dbg_context ( CONTEXT *context ); function which converts the context to a string, and then use directly TRACEs instead of pcontext. There are examples in the code on how to do so via the wine_dbg_sprintf() function. See ./dlls/x11drv/xvidmode.c around line 460, in the _CDS_flags() function. -- Dimi.

May 2, 2003

Re: New metabugs

by hatky

--- Dan Kegel <dank(a)kegel.com> wrote: > Hatky wrote: > > Ok so mybe the fix-me/stub/unimplemented bugs > category > > is a really bad idea but we are having diffrent > > opinions on the more general idea of using > metabugs as > > categories... > > Hi Hatky, > I appreciate the energy you're bringing to the wine > project! Thanks a lot. > > That said, it might be a good idea for you to tread > lightly > at least at first in the winehq bugzilla. Tread lightly? you mean little changes insted of the full reorginaztion I was trying to make? > Like you, > I just > started contributing to a bugzilla (OpenOffice's), > and > the guys there are probably as nervous about me > messing > with their bugzilla as I am about you messing around > in > Wine's bugzilla! So I'm being cautious, and instead > of > creating a metabug right off the bat, I created some > canned > queries and links to bugs on my own web site > (http://www.kegel.com/openoffice/) > to try out my ideas first. And when the openoffice > qa mailing > list folks say "yeah, go ahead and create a > metabug", I will - > but one at a time, and gently. > > Anyway, don't let me slow you down. Just remember > that > bug tracking is a social issue, and you have to pay > attention > to how the other developers feel about it. I am not sure what they realy think yes I only got 3 responces 2 of witch where positive :)... I guess I will have to wait for the next week to start when codewaver will return to flame me (or not) :) I was also helping close a few bugs and I am sure that is not bad :). > > Cheers, > Dan > > -- > Dan Kegel > http://www.kegel.com > http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045 > > Thank for your toughts, Hatky. __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com

May 2, 2003

Re: New metabugs

by Dan Kegel

Hatky wrote: > Ok so mybe the fix-me/stub/unimplemented bugs category > is a really bad idea but we are having diffrent > opinions on the more general idea of using metabugs as > categories... Hi Hatky, I appreciate the energy you're bringing to the wine project! That said, it might be a good idea for you to tread lightly at least at first in the winehq bugzilla. Like you, I just started contributing to a bugzilla (OpenOffice's), and the guys there are probably as nervous about me messing with their bugzilla as I am about you messing around in Wine's bugzilla! So I'm being cautious, and instead of creating a metabug right off the bat, I created some canned queries and links to bugs on my own web site (http://www.kegel.com/openoffice/) to try out my ideas first. And when the openoffice qa mailing list folks say "yeah, go ahead and create a metabug", I will - but one at a time, and gently. Anyway, don't let me slow you down. Just remember that bug tracking is a social issue, and you have to pay attention to how the other developers feel about it. Cheers, Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

May 2, 2003