November 2002 - Wine-Devel - list.winehq.org

Q CD Player 3
by Dimitrie O. Paun Nov. 5, 2002

Nov. 5, 2002

Another success story: http://www.quinnware.com/news.html See, we're not doing that bad! :) Besides, if we get the multimedia thingy working right, we'll impress quite a few people... -- Dimi.

2 1

Re: Wine 0.8 TODO v0.1
by Dimitrie O. Paun Nov. 5, 2002

Nov. 5, 2002

On November 2, 2002 10:11 am, Keith Matthews wrote: > Don't care how sexy it is or is not, only if it will work. Some of them > seem to be making some pretty specific assumptions about the interface > available, and doing it in the install routines too. Well, yeah, we should have the Mozilla thingy installed _before_ we install the program that depends on it, that's obvious. BTW, anyone care to take Mozilla Win32 for a spin under Wine, see if it works? -- Dimi.

2 1

RFC: rpcss skeleton prototype #2
by Greg Turner Nov. 5, 2002

Nov. 5, 2002

A couple of questions about headers... I wrote... > +#include <stdio.h> First, does this end up using the right "stdio.h"? It won't be an issue once I switch over to the real wine debug macros... but I wasn't sure if, by doing this, I was going to get the wine printf() or the unix printf()? I wanted the wine one, so should I have been doing #include "msvcrt/stdio.h" instead? When I tried this, I got a bunch of conflicts with my unix headers.... Does it matter? Second: > +#include "windows.h" would it be more general to do something like: #if defined(__WINE__) #include "windows.h" #else #include <windows.h> #endif Or is it OK, as is, for MSVC/cygwin? thanks for your patience and help, -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

2 1

Maximus 3.4 CD Player
by Dimitrie O. Paun Nov. 5, 2002

Nov. 5, 2002

Seems to install & run just fine: http://solair.eunet.yu/~muaddib Cool app! -- Dimi.

1 0

AxelCD
by Dimitrie O. Paun Nov. 5, 2002

Nov. 5, 2002

This one installs OK, and runs OK. And it's cool. I haven't tried playing CDs, but I think we should try to include it on the list. http://www.accelware.com/axelcd/ -- Dimi.

1 0

A2 Media Player
by Dimitrie O. Paun Nov. 5, 2002

Nov. 5, 2002

Installs OK, runs almost fine. This one is special in that the main window is supposed to be round, but we also create a rectangular window behind it. I think we should try to get this one to Gold. http://thenewsmonsters.tucows.com/mmedia/preview/193593.html -- Dimi.

1 0

Re: RFC: rpcss skeleton prototype #2
by Greg Turner Nov. 5, 2002

Nov. 5, 2002

I wrote... > > #include "msvcrt/stdio.h" > oops, s/msvcrt/wine\/msvcrt/ ugh! I take it back! sorry. -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

1 0

Re: RFC: rpcss skeleton prototype #2
by Greg Turner Nov. 5, 2002

Nov. 5, 2002

I wrote... > #include "msvcrt/stdio.h" oops, s/msvcrt/wine\/msvcrt/ -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

1 0

WineHQ menu (take 3)
by Francois Gouget Nov. 4, 2002

Nov. 4, 2002

Here's the latest version of my WineHQ menu proposal. I tried to take into account (at least some of) the comments I received on the previous one. What's especially new is that you can see this one on the Web and that should give everyone something more concrete to think about. Note of course that it's just a draft so it comes with disclaimers: - I did not reorganize anything in the Web site so the links may not take you were you expect. In particular they will systematically send you to the 'old' site. - the presentation is a patchwork of stuff taken from WineHQ's bugzilla and WineHQ's home page and about the only screenshot that we have. So the look and feel is far from consistent. But I want you to imagine in your mind that it all matches pretty well. Now that you've read the disclaimer you can have a look at it: http://fgouget.free.fr/tmp/WineHQ.html And now, I'll add more comments: * Ok, first I should not have said 'on the home page the news should be a link and no more'. That's not even really what I think. I still think it's absolutely vital that the home page answer the question 'What is Wine?'. But once that is answered, there is room left for the latest news, a pointer to the latest WineHQ release, etc. See the above URL for a possible (if maybe somewhat clumsy) layout. * The '7' item limit. I think it only applies to flat lists. The menu structure I propose never has more than 7 items in a category and does not have more than 7 categories. I will also note that the Application Database has 14 items, and the Bugzilla page more than 40 and both are perfectly usable. The Home Page (and most other pages) will only have 30 now and I think that fits pretty well. * I renamed 'Contributing' to 'Help Wanted' which hopefully is clearer. * 'Supported Applications'. That's too long: it gets split in two lines so I shortened it to 'Applications'. We could also make our menus larger or rename it to 'Application Support' (which would still require making the menu a bit larger). * Manually maintained 'Supported Applications' list. I did not add a menu entry for this. However, maybe this could be the home page of the Application Database. * removed 'Miscellaneous'. Community and Related Projects become sections of the Wine Introduction (f and h). The Legal item in fact just contained the Wine license. I think it should be visible somewhere so I renamed it to 'License', and it becomes item 7 of 'About Wine'. The Contacts item disappears from the menu and should now be part of whatever standard footer we add to the pages. Menu hierarchy -------------- 1. About Wine 1.1. Introduction a. Intro b. Why Wine c. Myths d. Technology e. History f. Community g. Companies h. Related projects 1.2. Screenshots 1.3. Supported Applications 1.4. Help Wanted a. Application maintainer b. Bug triage c. Website maintenance d. Development 1.5. News 1.6. Press 1.7. License 2. Download 2.1. Binaries 2.2. Source 3. Support 3.1. FAQ 3.2. Howto 3.3. Bug Tracking 3.4. Troubleshooting 3.5. Forums a. Mailing Lists b. Newsgroup c. IRC Channel 4. Documentation 4.1. User Guide 4.2. Developer Guide 4.3. Packager Guide 4.4. API Docs 5. Development 5.1. CVS (instructions for using CVS, pointer to CVS Web) 5.2. Developer Hints 5.3. Submitting Patches 5.4. TODO Lists - 0.9/1.0 TODOs - Tasklist/bug 395 - FIXMEs/bug 455, - Tasklets/bug 406 - most wanted bugs 5.5. Status 5.6. Resources a. LXR b. CVS Web c. Who's Who d. Tools e. Win32 Documentation, X doc, etc. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ We are Pentium of Borg. You will be approximated. Division is futile.

5 7

Re: A problem with comctl32
by Rolf Kalbermatter Nov. 4, 2002

Nov. 4, 2002

DanteAliegri <dantealiegri(a)umbc.edu> wrote: >Hey, I've come across what appears to be a >simple problem in comctl32. >When running icq99b, wine was dying in imagelist.c while trying to >dereference a null pointer. >Upon looking at the file, there was code for returning FALSE if that >pointer was null, thus I felt it being null may be a valid choice. >I made the attached change, and the problem was fixed. >Comments? > >--- imagelist.c 23 Oct 2002 22:19:11 -0000 1.65 >+++ imagelist.c 2 Nov 2002 20:40:53 -0000 >@@ -1082,11 +1082,14 @@ > HBITMAP hImageBmp, hOldImageBmp, hOldImageListBmp, hOldMaskListBmp, >hBlendMaskBmp; > BOOL bIsTransparent, bBlend, bResult = FALSE; > const HIMAGELIST himl = pimldp->himl; ^^^^^^^^^^^^ According to the same lines pimldp could also be NULL so this might as well cause a NULL pointer dereference and should be moved to after the check for "if (!pimldp || !(himl = pimldp->himl)) return FALSE; Of course the question remains why would you call the function at all with a NULL pointer. >- const INT lx = himl->cx * pimldp->i + pimldp->xBitmap; >- const INT ly = pimldp->yBitmap; >+ static INT lx; >+ static INT ly; Should this be really static? Can't this function be called reentrant? > if (!pimldp || !himl) return FALSE; > if ((pimldp->i < 0) || (pimldp->i >= himl->cCurImage)) return FALSE; >+ >+ lx = himl->cx * pimldp->i + pimldp->xBitmap; >+ ly = pimldp->yBitmap; Rolf Kalbermatter

2 1