March 2011 - Wine-Devel - list.winehq.org

Re: Ubuntu's next release and raising hard ulimit on ubuntu

by Paul Chitescu

On Friday 25 March 2011 03:26:25 pm Dan Kegel wrote: > Scott, correct me if I'm wrong, but does Natty still have the > hard limit of 1024 files open per process? > If so, should be ask people to go vote for > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/663090 > ? > > Getting that limit raised might avoid increasing numbers of > support requests from users who can't figure out why Wine can't run their > p2p downloader ( http://bugs.winehq.org/show_bug.cgi?id=25015 ). This is not an Ubuntu limitation but rather of the (g)libc API implementation. At least on glibc it is possible to increase the FD_SETSIZE at build time. Been there, done that, got the T-shirt. No need for header patching. http://yate.null.ro/websvn/filedetails.php?repname=yate&path=%2Ftrunk%2Feng… Caveat: FD_... operations take longer if FD_SETSIZE is increased. On all relevant platforms it is possible to check if a fd is above the limit. The application code must do so. Best is to internally replace select() with poll() on platforms that support it.

March 25, 2011

Ubuntu's next release and raising hard ulimit on ubuntu

by Dan Kegel

Scott, correct me if I'm wrong, but does Natty still have the hard limit of 1024 files open per process? If so, should be ask people to go vote for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/663090 ? Getting that limit raised might avoid increasing numbers of support requests from users who can't figure out why Wine can't run their p2p downloader ( http://bugs.winehq.org/show_bug.cgi?id=25015 ).

March 25, 2011

Re: [PATCH 07/15] d3dx9: Add ID3DXBaseEffect interface.

by Rico Schüller

Am 24.03.2011 12:12, schrieb Henri Verbeet: > 2011/3/23 Rico Schüller<kgbricola(a)web.de>: >> + FIXME("íface %p, desc %p stub\n", This, desc); > Typo? > Yes, that's a typo. I'll improve the patch and I'll fix all occurrences. Thanks Rico

March 25, 2011

Re: [PATCH 03/15] d3dx9: Use size of variable instead of type.

by Rico Schüller

Am 23.03.2011 12:00, schrieb Nikolay Sivov: > On 3/23/2011 13:49, Rico Schüller wrote: >> --- >> dlls/d3dx9_36/effect.c | 4 ++-- >> 1 files changed, 2 insertions(+), 2 deletions(-) >> len = MultiByteToWideChar(CP_ACP, 0, srcfile, -1, NULL, 0); >> - srcfileW = HeapAlloc(GetProcessHeap(), HEAP_ZERO_MEMORY, len * >> sizeof(WCHAR)); >> + srcfileW = HeapAlloc(GetProcessHeap(), HEAP_ZERO_MEMORY, len * >> sizeof(*srcfileW)); >> MultiByteToWideChar(CP_ACP, 0, srcfile, -1, srcfileW, len); > No need to zero, if it will be filled with next call. This could a > subject of next patch of course. > > Yeah, I'll send a patch for that one. Thanks for the hint. Cheers Rico

March 25, 2011

Re: d3dx10: Float16To32Array and Float32To16Array (GSoC)

by Joshua Beck

On 03/20/2011 05:42 PM, Stefan Dösinger wrote: > Wrt this specific function we already have some related infrastructure for > D3DXLoadSurfaceFrom* . Also other parts of Wine(gdi32.dll, windowscodecs.dll) > have functions for handling various on-disk file formats which can(and should) > be used. (That's just some generic implementation hint, it doesn't mean that > it makes the idea good or bad) > Is there any documentation I can read on how to program for these DLLs? I've been looking through MSDN and I can't find anything specifically about those DLLs. However I did find Windows Imaging Component (which I think is what windowscodecs.dll implements) and that seems like it would be helpful for the D3DXSaveSurfaceTo* functions.

March 25, 2011

Re: [GSoC] Merge winecfg and Control Panel

by wine.dev＠web.de

Dear Tony Welcome to Wine. > > After all the searches, I still do not have an overall idea of how to > create an control panel applet. From my current understanding, if I put the > cpl (dll) file in "~/.wine/drive_c/windows/system32/", wine control will > recognize it automatically, right? When you add a new cpl, the wine build system does this for you. > If so, is there any instructions on how to build a simple applet under wine > (even one that does nothing could work for me). I'd really like to try > create and build some test applet in order to understand it better. As always: Read the source. What you try to do (test applet) is how i started with inetcpl.cpl a while ago. git has a web interface with a history and the first commit for inetcpl.cpl is a minimalistic control applet. ( http://source.winehq.org/git/wine.git/history/HEAD:/dlls/inetcpl.cpl ) -- by by ... Detlef

March 25, 2011

Re: [GSoC] Merge winecfg and Control Panel

by Vincent Povirk

You can pretty much ignore everything in the actual C source files of appwiz.c except the CPlApplet function. CPL_STARTWPARMSW is unimportant, and all CPL_DBLCLK does is create a window. The only difference from the layout of a normal Windows program is that a control panel applet does not include its own message loop. The caller takes care of that. See also http://msdn.microsoft.com/en-us/library/bb776392%28VS.85%29.aspx

March 25, 2011

Re: [GSoC] Merge winecfg and Control Panel

by Tony Zhang

Dear Owen, > Actually creating a new control panel applet is a fairly straightforward > task. You can look at the existing control panels (appwiz.cpl, inetcpl.cpl) > to get an idea of what's involved > > After all the searches, I still do not have an overall idea of how to create an control panel applet. From my current understanding, if I put the cpl (dll) file in "~/.wine/drive_c/windows/system32/", wine control will recognize it automatically, right? If so, is there any instructions on how to build a simple applet under wine (even one that does nothing could work for me). I'd really like to try create and build some test applet in order to understand it better. Sorry for taking your time. Thanks in advance. Best, -- Tony (Chi Zhang)

March 24, 2011

Re: GSoC: Implement the Explorer

by John Klehm

On Thu, Mar 24, 2011 at 9:51 AM, David Hedberg <david.hedberg(a)gmail.com> wrote: > Hi Jay, > > On Thu, Mar 24, 2011 at 05:16, Jay Yang <jkelleyy(a)gmail.com> wrote: > As for TortoiseSVN I don't dare speak for what others might find > useful or how far we are from having that working, but in general Pretty much a drop in linux replacement for tortoise is RabbitVCS: http://www.rabbitvcs.org/

March 24, 2011

Re: [GSoC] Merge winecfg and Control Panel

by Tony Zhang

Dear Owen, > Actually creating a new control panel applet is a fairly straightforward > task. You can look at the existing control panels (appwiz.cpl, inetcpl.cpl) > to get an idea of what's involved > > I have looked at the two existing applets, but got a little confused by the variable names and the organization of the files (the call chain). I'm able to find some documents talking about how to create control panel applet in Windows CE (haven't got time to read them through). Is that similar to creating cpl in wine? -- Tony (Chi Zhang)

March 24, 2011

Re: wine 1.3.16: wrc compiler and LANGUAGE

by Austin English

On Thu, Mar 24, 2011 at 14:25, Gilles Depeyrot <gsd(a)dolphin.fr> wrote: > On 24/03/2011 08:06, Dmitry Timoshkov wrote: >> >> Gilles Depeyrot<gsd(a)dolphin.fr> wrote: >>> >>> Has there been a change between wine 1.2.2 and wine 1.3.x that would >>> require adding an include file that was previously not needed? >> >> I don't think so. Including windef.h and winuser.h should be enough. >> If you could provide a small .rc file and command line you are using >> that would help in figuring out the problem. > > With the attached files and the following command line the resource file is > compiled using wine 1.2.2 and fails using wine 1.3.16. > > wrc -I$WINEHOME/include/wine/msvcrt -I$WINEHOME/include/windows -fofoo.res > foo.rc Using git bisect run ./wrc.sh: #!/bin/bash ./configure --disable-tests || exit 125 make -j15 || exit 125 ./tools/wrc/wrc -I$WINEHOME/include/wine/msvcrt -I$WINEHOME/include/windows -fofoo.res foo.rc revealed the bad commit to be: e6340f1652e0328bbfeeae58462f41400b09b38a is the first bad commit commit e6340f1652e0328bbfeeae58462f41400b09b38a Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Sep 29 20:13:28 2010 +0200 wrc: Add support for target options, and define _WIN64 for 64-bit builds. :040000 040000 af53e5447fca71246cd4f4ec1cd91887f6c3eee2 19d82ada48a0b03253cf7a315cfd656f7c6c4be3 M tools though this belongs in bugzilla, not wine-devel. -- -Austin

March 24, 2011

Re: GSoC: Implement the Explorer

by David Hedberg

Hi Jay, On Thu, Mar 24, 2011 at 05:16, Jay Yang <jkelleyy(a)gmail.com> wrote: > Hello, > > Since my first proposal got no response at all, I thought I'd offer > another possible project I'm interested in. I looked a little into the > "Implement the Explorer" project idea listed on the Summer of Code page on > the wine wiki. I have a few questions as to what parts need to be > implemented. Clearly, as stated by the description on the Summer of Code > page, we have winefile, which does some of the things expected of explorer, > but how far is winefile from a correct explorer implementation? Also would > implementing Shell Extensions be a good Summer of Code project? In > particular, I think it would be nice to have things like TortiseSVN working > in wine. > I think winefile is pretty much a dead end as far as "correct" Explorer implementations go. Assuming that we want something as close to the native architecture as possible, the main functionality of the windows explorer lies in libraries ( shell32.dll, explorerframe.dll, ..), used through COM. I did some work in this area last year, which resulted in an implementation of the ExplorerBrowser control (see the documentation for IExplorerBrowser on msdn [1]). I also just now quickly fixed up the proof-of-concept "explorer" I hacked up last year so that it at least compiles on my system (see [2]). It's not beautiful (neither the code nor the interface), but it might give you an idea of what the current state of affairs are. It runs on at least wine and Windows 7, and should also run on Vista. The code for creating new explorer windows should probably reside in explorerframe.dll, somewhat analogous to how this works for the Internet Explorer and shdocvw.dll. As for TortoiseSVN I don't dare speak for what others might find useful or how far we are from having that working, but in general there's no lack of things in the shell subsystem that could use some attention. Having explorer implemented and somewhat working would undoubtedly also lead to more of these shortcomings surfacing and hopefully getting some attention. [1] http://msdn.microsoft.com/en-us/library/bb761909%28v=vs.85%29.aspx [2] http://inget.dyndns.org:9999/wine_explorer/ -- David

March 24, 2011

Re: wine 1.3.16: wrc compiler and LANGUAGE

by Gilles Depeyrot

On 24/03/2011 08:06, Dmitry Timoshkov wrote: > Gilles Depeyrot<gsd(a)dolphin.fr> wrote: >> Has there been a change between wine 1.2.2 and wine 1.3.x that would >> require adding an include file that was previously not needed? > I don't think so. Including windef.h and winuser.h should be enough. > If you could provide a small .rc file and command line you are using > that would help in figuring out the problem. With the attached files and the following command line the resource file is compiled using wine 1.2.2 and fails using wine 1.3.16. wrc -I$WINEHOME/include/wine/msvcrt -I$WINEHOME/include/windows -fofoo.res foo.rc Best regards, Gilles

March 24, 2011

Re: [GSoC] Implementing missing DirectInput8 features

by Vitaliy Margolen

On 03/23/2011 02:52 PM, Lucas Zawacki wrote: > Hello, I'm Lucas Fialho Zawacki a Computer Science undergrad at UFRGS > university in Brazil. I'm very interested in working with Wine for the > Google Summer of Code and have decided to approach the implementation > of DirectInput8 missing features. Welcome to Wine development! > At the moment, I don't have a clear understanding of how the > implementation should be done There are number of things that are missing in Wine's dinput8. Two that are mentioned on ideas page - Action Mapping and Enumeration by Semantics are more of data gathering then much coding. Of course there are number of stubs that could be implemented as well. Vitaliy.

March 24, 2011

Re: browseui/tests: COM cleanup in autocomplete.c.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=10131 Your paranoid android. === WNT4WSSP6 (32 bit autocomplete) === autocomplete.c:250: Test failed: CoCreateInstance(&CLSID_ACLMulti, NULL, CLSCTX_INPROC, &IID_IEnumString, (LPVOID *)&obj) failed: 80040154

March 24, 2011

Re: [PATCH 07/15] d3dx9: Add ID3DXBaseEffect interface.

by Henri Verbeet

2011/3/23 Rico Schüller <kgbricola(a)web.de>: > + FIXME("íface %p, desc %p stub\n", This, desc); Typo?

March 24, 2011

Re: wine 1.3.16: wrc compiler and LANGUAGE

by Dmitry Timoshkov

[please bottom post] Gilles Depeyrot <gsd(a)dolphin.fr> wrote: > Has there been a change between wine 1.2.2 and wine 1.3.x that would > require adding an include file that was previously not needed? I don't think so. Including windef.h and winuser.h should be enough. If you could provide a small .rc file and command line you are using that would help in figuring out the problem. -- Dmitry.

March 24, 2011

Re: wine 1.3.16: wrc compiler and LANGUAGE

by Gilles Depeyrot

Hi, Has there been a change between wine 1.2.2 and wine 1.3.x that would require adding an include file that was previously not needed? Thanks, Gilles On 24/03/2011 06:29, Dmitry Timoshkov wrote: > Jerome Leclanche<adys.wh(a)gmail.com> wrote: > >> I don't think SUBLANG_FRENCH is valid in rc files. Have you tried >> SUBLANG_NEUTRAL? > SUBLANG_FRENCH is valid, probably he is missing some include files. > -- Gilles Depeyrot - MEDAL Development Manager DOLPHIN Integration "The Enabler of mixed signal Systems-on-Chip" BP 65 Inovallée F-38240 Meylan FRANCE Tel: +33 (0)476 41 74 01 Fax: +33 (0)476 90 29 65 mailto:gsd(a)dolphin-integration.com http://www.dolphin-integration.com

March 24, 2011

Re: wine 1.3.16: wrc compiler and LANGUAGE

by Gilles Depeyrot

Hi, It is valid for the Microsoft resource compiler and also for wine 1.2.2. Gilles On 23/03/2011 23:54, Jerome Leclanche wrote: > I don't think SUBLANG_FRENCH is valid in rc files. Have you tried > SUBLANG_NEUTRAL? > > > J. Leclanche > > > > On Wed, Mar 23, 2011 at 9:54 AM, Gilles Depeyrot<gsd(a)dolphin.fr> wrote: >> Hi, >> >> I am testing compiling an application that uses winelib with 1.3.16 >> (currently compiled with 1.2.2). >> >> I have an issue with the resource compiler (wrc) which doesn't understand >> the LANGUAGE line. When I compile resource files, I get errors resembling: >> >> file.rc:22:21: Error: syntax error >> >> The corresponding line in the file is: >> >> LANGUAGE LANG_FRENCH, SUBLANG_FRENCH >> >> If I comment the line, the compilation succeeds. >> >> Best regards, >> Gilles >> >> >> -- Gilles Depeyrot - MEDAL Development Manager DOLPHIN Integration "The Enabler of mixed signal Systems-on-Chip" BP 65 Inovallée F-38240 Meylan FRANCE Tel: +33 (0)476 41 74 01 Fax: +33 (0)476 90 29 65 mailto:gsd(a)dolphin-integration.com http://www.dolphin-integration.com

March 24, 2011

Re: wine 1.3.16: wrc compiler and LANGUAGE

by Dmitry Timoshkov

Jerome Leclanche <adys.wh(a)gmail.com> wrote: > I don't think SUBLANG_FRENCH is valid in rc files. Have you tried > SUBLANG_NEUTRAL? SUBLANG_FRENCH is valid, probably he is missing some include files. -- Dmitry.

March 24, 2011

GSoC: Implement the Explorer

by Jay Yang

Hello, Since my first proposal got no response at all, I thought I'd offer another possible project I'm interested in. I looked a little into the "Implement the Explorer" project idea listed on the Summer of Code page on the wine wiki. I have a few questions as to what parts need to be implemented. Clearly, as stated by the description on the Summer of Code page, we have winefile, which does some of the things expected of explorer, but how far is winefile from a correct explorer implementation? Also would implementing Shell Extensions be a good Summer of Code project? In particular, I think it would be nice to have things like TortiseSVN working in wine. Thanks -- Jay Yang

March 23, 2011

Re: winex11.drv/opengl.c: add improved error handling to pglXMakeCurrent() call

by Chris Robinson

On Wednesday, March 23, 2011 9:00:25 PM Joshua Beck wrote: > This patch was made against the origin, so if you've applied my previous > patch, remove that one before applying this one. > This patch makes the error message use ERR_(winediag) instead of just > ERR and is closer in style to the other error messages in opengl.c. There's some trailing whitespace in the patch.

March 23, 2011

Re: winex11.drv/opengl.c: add error handling to pglXMakeCurrent() call

by Roderick Colenbrander

Hi Joshua, Was about to submit a similar patch (had a few tiny fixes in my tree left), but this patch is mostly fine with me. Except I would print to 'winediag' like some of the other errors for software / indirect rendering are doing. So do something like 'Unable to active OpenGL context, like something your drivers have not been configured properly' (look what the other messages are like). Roderick On Thu, Mar 24, 2011 at 2:34 AM, Joshua Beck <jxb091000(a)utdallas.edu> wrote: > This patch should make it easier for those with driver problems to find the > problem when running Wine. > --Josh > > > >

March 23, 2011

Re: Duplicate AppDB Entry

by Rosanne DiMesio

On Wed, 23 Mar 2011 17:57:01 -0700 Jeremy Nowka <jnowka(a)gmail.com> wrote: > "Barnes And Noble EReader" v2.5 and "Nook for PC" are the same program. I > feel that the two AppDB entries should be combined for easier access by the > general public. I feel that the information should be merged to "Nook for > PC" because this is the common name for version 2.5. The version number for > "Nook for PC" should be changed to reflect the actual version, 2.5. Done. -- Rosanne DiMesio <dimesio(a)earthlink.net>

March 23, 2011

Duplicate AppDB Entry

by Jeremy Nowka

"Barnes And Noble EReader" v2.5 and "Nook for PC" are the same program. I feel that the two AppDB entries should be combined for easier access by the general public. I feel that the information should be merged to "Nook for PC" because this is the common name for version 2.5. The version number for "Nook for PC" should be changed to reflect the actual version, 2.5.

March 23, 2011