WineConf 2005: hotel info

2005-01-22 Thread Brian Vincent
Earlier I added hotel info to the WineConf pages: http://www.winehq.com/site/wineconf/travel Here's what you need to know: - we have 50 rooms reserved for Fri and Sat night, we have some on Thursday and Monday night too. I'll drink bier with anyone arriving early or staying late. - 81 EUR for

Re: where does windows define RTL_RWLOCK?

2005-01-22 Thread Andreas Mohr
Hi, On Sat, Jan 22, 2005 at 04:21:11PM -0500, Robert Reif wrote: > I'm trying to compile wine's direct sound dll on windows > and I can't get past this problem. I can't find a windows > file that defines RTL_RWLOCK in the PSDK or DDK. > > Is the structure wine uses compatible with windows? I didn

Re: More DCOM notes

2005-01-22 Thread Rob Shearman
Mike Hearn wrote: Here are some more notes in a convenient to read form. I'll turn these into a documentation patch later. Rob, can you double-check this? This document assumes you are familiar with the basics of DCOM. If you aren't read this first: http://winehq.com/site/docs/wine-devel/dcom-1 Thi

where does windows define RTL_RWLOCK?

2005-01-22 Thread Robert Reif
I'm trying to compile wine's direct sound dll on windows and I can't get past this problem. I can't find a windows file that defines RTL_RWLOCK in the PSDK or DDK. Is the structure wine uses compatible with windows?

Compiling the MFC using Winelib

2005-01-22 Thread Dan Dennison
Building MFC for winelib has been addressed many times earlier on this list, from what I can see, since at least 2001 if not earlier. However, all together I cannot seem to find a well-written documentation of the process involved to build libmfc.so. So as a service to the Wine community I plan to

Re: [DSOUND] fix memory leak in mixer code

2005-01-22 Thread Robert Reif
Robert Reif wrote: Fix memory leak in mixer code. Revised to remove unnecessary test before HeapFree. Index: dlls/dsound/dsound.c === RCS file: /home/wine/wine/dlls/dsound/dsound.c,v retrieving revision 1.24 diff -u -p -r1.24 dsound

More DCOM notes

2005-01-22 Thread Mike Hearn
Here are some more notes in a convenient to read form. I'll turn these into a documentation patch later. Rob, can you double-check this? This document assumes you are familiar with the basics of DCOM. If you aren't read this first: http://winehq.com/site/docs/wine-devel/dcom-1 This is not suitab

Re: [DSOUND] fix memory leak in mixer code

2005-01-22 Thread Mike Hearn
On Sat, 22 Jan 2005 14:46:04 -0500, Robert Reif wrote: > + if (This->tmp_buffer) > + HeapFree(GetProcessHeap(),0,This->tmp_buffer); There's no need for the test here, it's duplicated inside HeapFree. There was a janitorial task to clean this up not that long ago. thanks -mike

Re: Howto process X11 events async'ly

2005-01-22 Thread Mike Hearn
On Sat, 22 Jan 2005 11:23:31 -0600, Robert Shearman wrote: > It looks like we do the equivalent of select on the result from > ConnectionNumber. I have no idea what this is, but hopefully you might. > Grep the sources for "display_fd". I think all toolkits do this: just have a main loop based on

Re: Howto process X11 events async'ly

2005-01-22 Thread Robert Shearman
Peter Quiring wrote: I'm developing my own library and I'm in the process of porting it over in Linux. I can get X11 to display the graphics and process events, but the only problem I have is with processing events without wasting CPU power. How do you process events without constantly polling?

Re: Wine/Winelib for Visual Basic 6.0 Users?

2005-01-22 Thread Mike Hearn
On Fri, 21 Jan 2005 23:43:59 -0800, Ira Krakow wrote: > I was wondering - I'd like to include a section for > Visual Basic 6.0 users. Beyond running the .EXEs in > Wine, is it possible to use Winelib to convert VB6.0 > apps? No, there are no free/Linux Visual Basic compilers. Gambas is VB-like, i

Howto process X11 events async'ly

2005-01-22 Thread Peter Quiring
I'm developing my own library and I'm in the process of porting it over in Linux. I can get X11 to display the graphics and process events, but the only problem I have is with processing events without wasting CPU power. How do you process events without constantly polling? What I've done is

Re: MSI: indentation and style cleanup

2005-01-22 Thread Mike Hearn
On Fri, 21 Jan 2005 22:02:00 +0100, Michael Stefaniuc wrote: > Well, it should be pretty easy to write a short smatch script to find > that occurences. Afair the smatch guys wrote one for the Linux kernel > which would need only small adaptations. OOM safety is a bit complicated, you have to pro

Re: [d3drm] Adds a header, and corrects a typo

2005-01-22 Thread Ivan Leo Puoti
I didnt even think about copyrighting the 4 lines; I just copied it from another include file. The don't put a copyright line there at all. Ivan.

Updating my address book

2005-01-22 Thread Dustin
Hi I am updating my address book and it would be very helpful if you could click on the link below and enter your contact details for me: http://www.bebo.com/fr2/979448a934523b19214292c927616713d18 I am using a service that keeps contact details current, just update your own contact details

Re: [d3drm] Adds a header, and corrects a typo

2005-01-22 Thread Peter Berg Larsen
> >> + * Copyright (C) the Wine project On Fri, 21 Jan 2005, Tom wrote: > Why not just - the line you don't have to give copyright notice if you > don't want to. I didnt even think about copyrighting the 4 lines; I just copied it from another include file. > Ivan Leo Puoti wrote: > > Please us

cleanup shlfileop.c

2005-01-22 Thread Joris Huizer
Changelog: - use retCode smarter (undoing a few bits of myself) - add file_operation_invalid_handle(), file_operation_on_data(), file_operation_invalid_attr() instead of inline code I put back the line the discussion was about - I thought about it and I probably was not thinking the right way; If t

Re: Wine/Winelib for Visual Basic 6.0 Users?

2005-01-22 Thread Stefan Dösinger
Am Samstag, 22. Januar 2005 08:43 schrieb Ira Krakow: > I'm writing the Winelib part of the book. The main > audience is Microsoft Visual C++ 6.0 users. I can > define a development environment for both MFC and > non-MFC users, since it is well documented already. > > I was wondering - I'd like t