March 2004 - Wine-devel - list.winehq.org

filesystem changes break autofs patch
by Guido Draheim 31 Mar '04

31 Mar '04

To whoever is working on filesystem - let me remind you again (and again) that bsd autofs mountpoints do not exist until accessed - and they will not get created for removable media devices without a medium inserted, not even upon access / stat. Therefore, mapping "a:" to autofs'd "/vol/floppy" will not work in wine - any mapping to nonexistant mountpoint had been silently dropped in the past and btw one can not create a symlink to nonexistant point that easily. The unpatched wine has been unusable for autofs for a long time. I have been creating patches for a few years now integrating an option to ini file / registry but they were silently ignored. It is good if you are working again on the filesystem setup but please do not ignore autofs bsd-type automounter system! My patches do not work anymore, so I can not update to the lastest wine. I'll try to be patient and looking forward to your changes. -- guido http://google.de/search?q=guidod GCS/E/S/P C++/++++$ ULHS L++w- N++@ s+:a d(+-) r+@>+++ y++

1 0

RE: Handling dialogs created without using templates
by Santosh Siddheshwar 31 Mar '04

31 Mar '04

Hi, Do you have a solution to this issue? If yes, are you planning to introduce it soon? Thanks in advance. Regards Santosh Siddheshwar > -----Original Message----- > From: Dmitry Timoshkov [SMTP:dmitry(a)baikal.ru] > Sent: Tuesday, March 30, 2004 7:40 PM > To: Santosh Siddheshwar > Cc: wine-devel(a)winehq.com > Subject: Re: Handling dialogs created without using templates > > "Santosh Siddheshwar" <santosh.s(a)sonata-software.com> wrote: > > > Yes attached is a sample which is pretty similar to what I described > > below. > > Thanks. Now I see where the problem is. We have to hook dialog creation > code into common window creation code, something similar to what I've done > recently for MDI. Alexandre, are my thoughts correct? > > -- > Dmitry. ********************************************************************* Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. *********************************************************************

2 1

problem w/winebuild and '@' in names
by Jon Griffiths 31 Mar '04

31 Mar '04

Hi, winebuild doesn't support export names with an '@' correctly. When parsing the spec file, the @X is stripped. This causes names to be incorrectly listed as duplicates. I'm hitting this with mapi32.dll. Outlook 97 imports using get procaddress on the name including the '@', and some exports are given both with and without the '@' decoration. I'm working around this for mapi32 by commenting out remove_stdcall_decoration( odp->name ); at line 463 of parser.c. Is this a known problem, and is that the right solution? Cheers, Jon ===== "Don't wait for the seas to part, or messiahs to come; Don't you sit around and waste this chance..." - Live jon_p_griffiths(a)yahoo.com __________________________________ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html

4 4

Re: ALSA: Allow configuration of output devices to use and change standard output plugin requested to "default"
by felix.nawothnig＠t-online.de 30 Mar '04

30 Mar '04

On 03/26/2004 04:56:00 PM, Mike Hearn wrote: in ALSA_WaveInit(): > + wwo->device = ALSA_GetDeviceFromReg("PlaybackDevice"); in wodClose(): > + HeapFree(GetProcessHeap(), 0, wwo->device); and in widClose(): > + HeapFree(GetProcessHeap(), 0, wwi->device); Thats wrong. wods and wids can be reopened, ALSA_WaveInit is only called once. Caused... ALSA lib pcm.c:1906:(snd_pcm_open_noupdate) Unknown PCM 8ú<@ err:wave:wodOpen Error open: Success ALSA lib pcm.c:1906:(snd_pcm_open_noupdate) Unknown PCM 8ú<@ err:wave:wodOpen Error open: Inappropriate ioctl for device ...when my app. Commenting out the HeapFree()s fixes it. (I dunno where to put the HeapFree()s... but that's definitly the wrong place :)

2 1

Re: [LostWages] make winehq.org HTML 4.01 Transitional + XHTML 1.0 Transitional Valid
by Brian Vincent 30 Mar '04

30 Mar '04

> Dimi, I still don't get you, what you are saying is: > changing class=todo to class=done is considerably easier then > changing class="todo" to class="done" Rule #1: whoever is willing to do the thankless job of maintaining pages on the web site gets to tell anyone else how they'd like the formatting to be. Since this issue has directly affected me in the past I will point out a real argument for making this stuff compliant: If I copy and paste the HTML into a WWN it would be nice if I didn't have to do a ton of markup to make it well-formed. In fact, I almost never reference anything on WineHQ for that very reason. For example, in issue #143 I went through the markup for the original to-do list and corrected it (which is interesting to look at now, btw). Likewise, it's simple to copy things into the documentation. A good example of which is: http://www.winehq.com/site/status_options Parts of which may end up in the User Guide. But that's just me, and I ain't the one maintaining it. So if Dimi doesn't want it then I guess the best thing to do would be to resubmit with those parts left out. -brian

1 0

Re: [LostWages] make winehq.org HTML 4.01 Transitional + XHTML 1.0 Transitional Valid
by Dimitrie O. Paun 30 Mar '04

30 Mar '04

On Tue, 30 Mar 2004, hatky wrote: > Yes, this time with the patch... > > Change log: > Ofir Petruska <hatky(a)users.sf.net> > Validate the site as HTML 4.01 Transitional + XHTML 1.0 Transitional Valid > (still declaring declaring HTML 4.01 Transitional) > * Case fixes (all html tags should be lower case) > * Quote all attributes > * End empty tags as " />" Jeremy, Please don't apply this patch to the pages I maintain: TODO, Fun Projects, Janitorial, Winelib, Status | Options, Status | Porting As I've tried to explain in the past, these changes are totally unnecessary for manually maintained pages: it makes it harder to maintain, for the benefit of making it easier for the machine to parse. Bad tradeoff, especially given that we maintain these pages daily, and the machine has absolutely no problem parsing them. Thanks. -- Dimi.

2 1

RE: Handling dialogs created without using templates
by Santosh Siddheshwar 30 Mar '04

30 Mar '04

Hi, Yes attached is a sample which is pretty similar to what I described below. Regards Santosh Siddheshwar <<GetParent.zip>> > -----Original Message----- > From: Dmitry Timoshkov [SMTP:dmitry(a)baikal.ru] > Sent: Tuesday, March 30, 2004 12:51 PM > To: Santosh Siddheshwar > Cc: wine-devel(a)winehq.com > Subject: Re: Handling dialogs created without using templates > > "Santosh Siddheshwar" <santosh.s(a)sonata-software.com> wrote: > > > I have an application that creates dialogs without using any of the > Win32 > > Dialog creation APIs. I find that a lot of the > > functionality in DEFDLG_Proc (DM_SETDEFID, DM_GETDEFID & WM_NEXTDLGCTL) > is > > unavailable for use with > > dialogs created this way. This is because we allocate the DIALOGINFO > > structure only in the dialog creation APIs. Dialogs > > created without using these APIs have NULL DIALOGINFO structure. I also > find > > that allocating this structure and initializing > > the members of the structure will get around this problem. Does anyone > > visualize any problems with this approach? > > Also where would the best place to put such code? > > Do you have a small, self-contained sample code which demonstrates > what you have described? > > -- > Dmitry. ********************************************************************* Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. *********************************************************************

2 1

Handling dialogs created without using templates
by Santosh Siddheshwar 30 Mar '04

30 Mar '04

Hi, I have an application that creates dialogs without using any of the Win32 Dialog creation APIs. I find that a lot of the functionality in DEFDLG_Proc (DM_SETDEFID, DM_GETDEFID & WM_NEXTDLGCTL) is unavailable for use with dialogs created this way. This is because we allocate the DIALOGINFO structure only in the dialog creation APIs. Dialogs created without using these APIs have NULL DIALOGINFO structure. I also find that allocating this structure and initializing the members of the structure will get around this problem. Does anyone visualize any problems with this approach? Also where would the best place to put such code? Regards Santosh Siddheshwar ********************************************************************* Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. *********************************************************************

2 1

Re: [LostWages] make winehq.org HTML 4.01 Transitional + XHTML 1.0 Transitional Valid
by Maxime Bellengé 29 Mar '04

29 Mar '04

Hello, I think you forgot the patch On Tue, 2004-03-30 at 00:08, hatky wrote: > Change log: > Ofir Petruska <hatky(a)users.sf.net> > Validate the site as HTML 4.01 Transitional + XHTML 1.0 Transitional Valid > (still declaring declaring HTML 4.01 Transitional) > * Case fixes (all html tags should be lower case) > * Quote all attributes > * End empty tags as " />" -- Maxime Bellengé <maxime.bellenge(a)laposte.net>

2 1

Re: systray in desktop mode [unified resend]
by Mike Hearn 29 Mar '04

29 Mar '04

On Mon, 2004-03-29 at 22:19, Martin Fuchs wrote: > Then I don't see how you want to be able to handle shell applications > like Explorer and enable the systray icons in them. Explorer isn't really a useful app to run for us, so if systray handling doesn't work quite right for it we won't be losing sleep over it. However, we do want native shell32 to work, so it'll be using the same protocol. > Well, let's see how far Mike's upcoming rewritten systray can handle this. > I may have a look in the new code, and see if I it's possible to do it > without knowing about the desktop mode. Getting explorer/systray to work in Wine may not be easy, however ReactOS and Wine should be able to share the same shell32 which I think is the idea, yes?

2 1