October 2007 - Wine-Devel - list.winehq.org

Re: Wine Desktop Integration Code

by Roderick Colenbrander

> Out of curiousity, where can I find the code in the wine source that > handles creation of the Menu entries in Gnome and KDE. The creation of the entries is done by the wineshelllink script which is called by the shellink code from shell32 I think. Roderick -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger

Oct. 9, 2007

Re: make test drill

by Stefan Dösinger

Am Samstag, 6. Oktober 2007 20:28:36 schrieb Paul Vriens: > Jeremy White wrote: > > So, in a radical break from tradition, we're trying to > > accomplish something useful at Wineconf. > > > > Specifically, we're making 'make test' work for everyone, > > not just Alexandre. > > > > Maarten Lankhorst is maintaining a tree of all of our > > test related patches. > > > > So, for those that want to play, the thing to do is to > > git fetch git://repo.or.cz/wine/testsucceed.git master:testsucceed > > git rebase testsucceed > > > > Then you can do a make test (with a clean .wine directory) > > and share your results. It's useful to use Dan's filter: > > egrep '__test|make.*ok|Backtrace' <your-log-file-here> > > > > Up through the end of day tomorrow, you can send me the results > > of that egrep and I'll tally and triage. > > > > If you have a patch, send it in, and CC Maarten so he can > > update it. > > > > The goal is to have the number of failures as close to 0 > > as possible, and for the non 0 cases, to at least understand > > each failure. > > > > Cheers, > > > > Jeremy > > Hi, > > It's nice to fix all the test failures when running them in Wine. We > however have several tests that still fail on Windows so how can we be sure > the test results in Wine are correct? Some that are failing on a lot of > Windows boxes: I brought that up on WineConf, but I want to add it here too: It is a bit tricky to draw the line between a broken test and a badly set up Windows installation. There are situations where applications are broken on a specific Windows installation. As an example, d3d tests may fail when run in VMware. VMWare has a D3D to GL wrapper simmilar to Wine. This is some work in progress piece of code which fails to run many apps. So if the d3d test fails in VMWare then it is likely VMWare's bug. The problem can occur in other parts too, like an application overwriting system global libraries(aka DLL hell), or malware, copy protection rootkits, security apps, system tuners, etc. For example, there is a problem with Steam on Wine that occurs on Windows too, triggered by various tuning apps. So a failure on Windows doesn't necessarily mean that the test is wrong.

Oct. 9, 2007

Re: Wine Desktop Integration Code

by Lei Zhang

tools/wineshelllink ? On 10/9/07, EA Durbin <ead1234(a)hotmail.com> wrote: > > Out of curiousity, where can I find the code in the wine source that > handles creation of the Menu entries in Gnome and KDE. > ________________________________ > Peek-a-boo FREE Tricks & Treats for You! Get 'em! > > >

Oct. 9, 2007

Re: OpenGL child windows (bug 2398, fixed!)

by denis bonnenfant

I tested git version with solidworks, and now it's worse than with previous chris patch : - quite slow, just like with composite patch - highlighted lines offset, just like with composite patch - GLXbaddrawable crash when opening multiple windows, regression from the composite patch, that allows multiple windows It looks like all the previous issues are cumulated ! maybe I missed something ? Denis

Oct. 9, 2007

Re: Wine 1.0 bugs, release criteria

by Stefan Dösinger

Am Samstag, 6. Oktober 2007 13:41:43 schrieb Dan Kegel: > Over the next month or so, I'd like Wine developers to nominate important > bugs for 1.0 by setting their "target release" field to 1.0. Later on > we'll clean up and freeze the list somehow. I think all the remaining DirectDraw rewrite regressions, as well as most other regressions in the d3d area. I do not have a complete list of them. I'll make one when I'm done with my exam, but if people could point out their unfixed d3d regression bugs it would make my life easier and make sure the bugs do not stay behind.(My bug assignment / CC list should find all of them though)

Oct. 9, 2007

Wine Desktop Integration Code

by EA Durbin

Out of curiousity, where can I find the code in the wine source that handles creation of the Menu entries in Gnome and KDE. _________________________________________________________________ Peek-a-boo FREE Tricks & Treats for You! http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us

Oct. 9, 2007

Re: Window decorations missing on Compiz/Debian Etch

by Alexandre Julliard

Michael Jung <mjung(a)iss.tu-darmstadt.de> writes: > It seems that the added "data->whole_window" check in the expression > used to decide if a window has to be switched to managed mode causes > this problem for me. > > data->whole_window is set in create_whole_window at window.c:1002 > create_whole_window is called from X11DRV_CreateWindow at window.c:1292 > > data->whole_window is tested in X11DRV_SetWindowPos at winpos.c:251 > X11DRV_SetWindowPos is called form X11DRV_CreateWindow at window.c:1287 > > Thus, it seems to me that this check happens before > "data->whole_window" is initialized. Removing this check (as in the > attached patch) resolves the issue for me. But this does not seem to > be the correct solution, since the root desktop window is now flagged > as "managed", which does not have any impact (at least for me), but > which seem logically incorrect. That's just hiding the problem. If the window manager doesn't reevaluate the wm hints when the window is mapped, many things won't work. That's really a Compiz bug IMO. -- Alexandre Julliard julliard(a)winehq.org

Oct. 9, 2007

Re: [bugzilla] Upgrade from 3.0 to 3.0.2 .

by Alexandre Julliard

Jan Zerebecki <jan.wine(a)zerebecki.de> writes: > --- > See http://www.bugzilla.org/releases/3.0.2/release-notes.html and > http://www.bugzilla.org/status/changes.html for information about > the changes. > --- > If this patch is rejected from inclusion, please tell me why, as > I would have to ask anyway. Now that we are using a git repository, upgrades should be done by importing the new version to the upstream branch and doing a git merge, instead of applying a patch directly to the master branch. -- Alexandre Julliard julliard(a)winehq.org

Oct. 9, 2007

Re: request for kernel32/toolhelp windows testrun

by Hans Leidekker

On Monday 08 October 2007 23:25:06 Marcus Meissner wrote: > BUT I would like to test run it on windows first, so can someone > please run following patch against a real Windows? toolhelp.c:145: Test failed: new process at position 26 in snapshot, expected 1. toolhelp.c:146: Test failed: this process at position 25 in snapshot, expected 0. -Hans

Oct. 9, 2007

Request for "wine packages" bugzilla component

by Scott Ritchie

Sometimes we have bugs directly related to our packaging. It would be nice to have a bugzilla component for them, and perhaps automatically subscribe the package maintainers. Thanks, Scott Ritchie

Oct. 9, 2007