September 2006 - Wine-Devel

Re: include: Add new Vista SDK constants, fields and, structures documented at http://ian.joeuser.com/index.asp?AID=738
by Timo Kunze Sept. 11, 2006

Sept. 11, 2006

Alexandre Julliard <julliard(a)winehq.org> writes: > Francois Gouget <fgouget(a)free.fr> writes: >> > @@ -1707,6 +1732,7 @@ typedef struct tagTOOLINFOA { >> > LPSTR lpszText; >> > LPARAM lParam; >> > void *lpReserved; >> > + HBITMAP hbmp; >> > } TTTOOLINFOA, *LPTOOLINFOA, *PTOOLINFOA, *LPTTTOOLINFOA; > > I don't think our code is going to handle this properly. Before > extending the structures we need to fix places that depend on the size > of the old type. This website is absolutely outdated. Take a look at the current (build 5536) Windows SDK headers and you'll see, that e. g. the hbmp member of the TTTOOLINFO struct has been removed again. Regards Timo

1 0

Wineconf this weekend!
by Jeremy White Sept. 11, 2006

Sept. 11, 2006

Hi Folks, So this weekend is Wineconf, which is the mostly annual gathering of Wine developers and afficianodos. Everyone is welcome, although we do intend to run a very technical and developer focused agenda. It will be held in Reading, a bit west of London, in the UK. The formal program starts on Saturday. We have a tentative agenda posted on the Wiki here: http://wiki.winehq.org/WineConf2006 The one don't miss talk will be Alexandre's keynote, which will be at 9:00 am on Saturday. We're still working out the schedule for the other events. There is no charge, although you do have to take care of your own loding and travel. If you are planning to come, though, it would be handy if you could hit the RSVP page (if you haven't already): http://www.winehq.org/site/wineconf/rsvp That way we can make sure our catering counts aren't out of wack. If you are coming, particularly if you reserved a room on campus with me, you *must* sign up for this mailing list: http://www.winehq.org/mailman/listinfo/wineconf or you will miss out on important details, and you'll end up wandering around Reading desperately looking for your key. (And yes, that does mean I'll stop spamming this list, and start spamming that one :-/). Cheers, Jeremy

1 0

Re: dinput: [2/2] Create/destroy hook thread from DirectInput [try 3].
by Alexandre Julliard Sept. 11, 2006

Sept. 11, 2006

Vitaliy Margolen <wine-patch(a)kievinfo.com> writes: > +static void release_hook_thread(void) > +{ > + LONG ref; > + > + EnterCriticalSection(&dinput_hook_crit); > + ref = --hook_thread_refcount; > + TRACE("Releasing to %ld\n", ref); > + if (ref == 0) SendMessageW(hook_thread_hwnd, WM_DESTROY, 0, 0); WM_DESTROY is supposed to be sent by DestroyWindow, sending it manually is not very nice, you should use a WM_USER message instead. Also you need to clear hook_thread_hwnd first, otherwise there's a race since you don't wait for the thread to finish. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: Bug #4510: allowing -ansi for arpa/nameser.h in configure.ac
by Alexandre Julliard Sept. 11, 2006

Sept. 11, 2006

Joel Parker <jjk3(a)msstate.edu> writes: > This patch fixes bug #4510. It allows the use of -ansi when > running ./configure. I'm not sure I see the point, you'd need to fix all the places that use the file too, otherwise it won't compile, and it's not clear that defining BSD_SOURCE all over the place is a good idea. I'd suggest to fix the header instead. -- Alexandre Julliard julliard(a)winehq.org

2 2

Re: WINEDOCS: Update regression testing procedure to use Git
by Saulius Krasuckas Sept. 11, 2006

Sept. 11, 2006

* On Mon, 28 Aug 2006, Mike McCormack wrote: > Update regression testing procedure to use Git Any chances this patch gets into the webserver? :) http://marc.theaimsgroup.com/?l=wine-patches&m=115673906004873&w=2

2 1

Re: X11Drv: move WGL extension code
by Alexandre Julliard Sept. 11, 2006

Sept. 11, 2006

"Roderick Colenbrander" <thunderbird2k(a)gmx.net> writes: > The patch adds new WGL extension loading code based on code written > by an old opengl32 -> x11drv patch written by Tomas Carnacky. The > code properly advertises WGL extensions and only returns function > pointers when the extension is really available. It would be nicer to declare the extensions as constant variables instead of building everything at run time. Something like: static const struct wglextension swap_control = { "WGL_EXT_swap_control", { { "wglSwapIntervalEXT", X11DRV_wglSwapIntervalEXT }, { "wglGetSwapIntervalEXT", X11DRV_wglGetSwapIntervalEXT }, } }; static void load_extensions(void) { if (glxRequireExtension("GLX_SGI_swap_control")) register_extension( &swap_control ); ... etc. } Then the extension list can simply store a pointer instead of copying the whole thing once more, and you avoid a lot of nasty macros. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: include: Add new Vista SDK constants, fields and structures documented at http://ian.joeuser.com/index.asp?AID=738
by Alexandre Julliard Sept. 11, 2006

Sept. 11, 2006

Francois Gouget <fgouget(a)free.fr> writes: > @@ -1707,6 +1732,7 @@ typedef struct tagTOOLINFOA { > LPSTR lpszText; > LPARAM lParam; > void *lpReserved; > + HBITMAP hbmp; > } TTTOOLINFOA, *LPTOOLINFOA, *PTOOLINFOA, *LPTTTOOLINFOA; I don't think our code is going to handle this properly. Before extending the structures we need to fix places that depend on the size of the old type. -- Alexandre Julliard julliard(a)winehq.org

1 0

Making people aware about appdb and outdated Wine versions.
by killertux killertux Sept. 10, 2006

Sept. 10, 2006

Hello, I have problem... It's know as dublication of effort. Basicly there are sites that "compeate" with appdb it means HOWTOS, test result and everyting else are distributed in few thousands forums, wikis etc... Solution is that Wine should advertice Wine AppDB so people would actully use it rather than unoffical sites. So I would like to see some AppDB "adverticement" in winecfg. Winecfg about section is one good place to inform wonders of appdb but even better would be popup window when starting winecfg(at lest in first run) that informs about appdb. Normal users obtain copy of Wine trought their package manager and that means they do not know about appdb unless they they read it somewhere. This change must be done in order to kill useless stuff like this: http://forums.gentoo.org/viewtopic-t-496836.html Second: Old version of Wine are still quite used because of package managers just offers "stable" Wine versions over the "unstable" ones so I would like to see another popup or warning in winecfg that informs user that their Wine is getting old... so after specific number of days(from release of Wine version X) counter gives some warnings about old Wine version.

3 2

Re: Jonathan Ernst : winecfg: French translation update.
by Frank Richter Sept. 10, 2006

Sept. 10, 2006

On 10.09.2006 10:28, Alexandre Julliard wrote: > - LTEXT "This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.", > + LTEXT "Cette biblioth�que est un logiciel libre�; vous pouvez la redistribuer et/ou la modifier conform�ment aux dispositions de la Licence Publique G�n�rale GNU, telle que publi�e par la Free Software Foundation�; version 2.1 de la licence, ou encore (� votre choix) toute version ult�rieure." > IDC_STATIC,119,44,124,72 It seems that all (L)GPL translations are marked "unofficial" by the FSF. That's why I though it wouldn't be bad to put in a translated "This library is ..." but keep the original English notice as well for the German translation. -f.r.

2 1

Re: Re: Making people aware about appdb and outdated Wine versions.
by killertux killertux Sept. 10, 2006

Sept. 10, 2006

OK, if not popup then fixme or someting like if there is problems they can go to Wine AppDB to get some compatibility help. >> --SNIP-- >> Second: Old version of Wine are still quite used because of package >> managers just offers "stable" Wine versions over the "unstable" ones so I would like >> to see another popup or warning in winecfg that informs user that their Wine is >> getting old... so after specific number of days(from release of Wine version X) >> counter gives some warnings about old Wine version. > >Having a popup (or anything that requires user interaction) could get >really irritating - there are situations where people would use an >older version of wine on purpose. Like if a large organization uses it >to run one specific app, and has a specific version that works >perfectly, they might not have any reason to update. > >How about a fixme when wine is run, informing them that the version >they are running was released X long ago, and that if they have any >issues they should try a newer version? > >It'd be nice, too, if people then reported bugs with that on the top >of the output - it could save a lot of work chasing down already- fixed >issues. > >--Matt >

3 2