Re: DestroyMenu: Check if the menu is still used (fix for bug 1486)

"Michael Kaufmann" <[EMAIL PROTECTED]> wrote: > Some applications call DestroyMenu for menus that are still displayed in > a window. We need to check if a menu is still used and set the window's > menu handle to NULL if that's the case. > > This patch fixes the important bug 1486. > > Changel

Re: Wine and industrial communication like OPC

Rickard wrote: > * Juan Lang AND Robert Shearman - OPC doesn't use > named pipes. OPC uses Dcom over TCP. > * Mike Hearn - OPC doesn't need any new Windows > (2000, XP) parts, and should work on Win 98 with the > added Dcom support (not tested). Cool! This has a chance of working then. > * Did I

Is there any FAQ/Documentation for codebase familiarization? + Re: Create DLL stub files in c:\windows\system

-- codebase introduction/induction documentation, anything? -- Im new to the wine codebase and see several bugs I am wanting to handle, however my main concern at this immediate time is trying to sort out cross-compatability issues... I have completely hand-installed DirectX 9.0c at this time

Re: Create DLL stub files in c:\windows\system

On Sat, Sep 04, 2004 at 04:08:11PM +0100, Mike Hearn wrote: > On Sat, 2004-09-04 at 15:49, Vincent B??ron wrote: > > What we could do is if such a cross-compiler is detected at build time, > > use it to build PE dlls in addition to ELF dlls (or in place of? Not > > sure yet). If no cross-compiler i

Re: Drowning in FIXMEs...

On Sunday 05 September 2004 03:09 pm, Jukka Heinonen wrote: > Well, under DOS VGA text mode, mouse cursor is like "gpm" mouse > cursor, a character cell which gets inverted or otherwise > highlighted in order to show where mouse is currently located at. > As far as I know, neither Wine nor Window

shell32 unicodefy question

First of all I would like to check if there are any one working on this. Second Q: Some methods of IFSHelper interface defined as taking LPCSTR params. Is this right? I was unable to find any information in regards to this. And because this is exported interface I don't want to brake something tha

Re: Drowning in FIXMEs...

Chris Rankin: > OK, here's a first draft at a patch. Created with > reference to my old copies of Ralph Brown's Interrupt > List. Well, under DOS VGA text mode, mouse cursor is like "gpm" mouse cursor, a character cell which gets inverted or otherwise highlighted in order to show where mouse is

Re: Compile fix forinclude files from linux 2.6.7

On Sun, 5 Sep 2004 17:50:03 +0200, you wrote: > On Sun, Sep 05, 2004 at 05:38:03PM +0200, Rein Klazes wrote: > > Hi, > > > > Fix for bugzilla bug#2354, compile failure on Slackware 10. > > > > The include uses since Linux 2.6.7 a macro defined in > > . Compiler.h is new in linux 2.4.4, old but

Re: Drowning in FIXMEs...

> Check out the content of vga.c (in > dlls/winedos), you have most of the code you need. > However, int33 mouse hide/show should cooperate with > the vga layer. OK, here's a first draft at a patch. Created with reference to my old copies of Ralph Brown's Interrupt List. Cheers, Chris

Darwine Display Driver

Hi there everybody! First of all i have to admit that im quiet useless in coding, im just a user with _minimal_ programing knowledge, so this might sound like trash which we all should forget as soon as we can ;) When reading the article about porting wine to mac os and the related difficul

Re: Critical Sections Documentation Update

On Sunday 5 September 2004 13:26, Robert Shearman wrote: > - * Initialise a new RTL_CRITICAL_SECTION. > + * Initializes a new critical section. I'm afraid this critical section from your critical section patch will upset people in the critics' section ;-) -Hans

Re: weird ?clipping? errors

> I am wondering whether the code to do that should go in > PROPSHEET_SetCurSel rather than PROPSHEET_CanSetCurSel... I guess it would make more sense because CanSetCurSel seems like it should only check it it's possible to set current selection, and if it is possible, then SetCurSel will make the

Re: Compile fix forinclude files from linux 2.6.7

On Sun, Sep 05, 2004 at 05:38:03PM +0200, Rein Klazes wrote: > Hi, > > Fix for bugzilla bug#2354, compile failure on Slackware 10. > > The include uses since Linux 2.6.7 a macro defined in > . Compiler.h is new in linux 2.4.4, old but not very > old, so I added an autoconf check for such systems

Re: fixme:msi:MsiLocateComponentA installing dotnetredist.exe

On Sunday 05 September 2004 05:41 am, Hans Leidekker wrote: > > On the console, I saw only the four warnings/errors: > >fixme:msi:MsiInstallProductW L"/iH:\\IS3123.tmp\\netfx.msi" L"" > >fixme:msi:MSI_OpenDatabaseW open failed r = 80004005! > >Installation of /iH:\IS3123.tmp\netfx.msi (

Re: Wine bug with delphi Menus

Hi Robert This bug is a duplicate of bug 1486 which I've just fixed! :-) http://bugs.winehq.org/show_bug.cgi?id=1486 Regards Michael Hi people, I think I discovered a wine bug. In a delphi program, changing the visibility of a menuitem (TMenuItem) causes the whole menu of that form to stop working

Re: Wine and industrial communication like OPC

Thank you, for all your answers! We have one employee who has worked a lot with Windows, and same with OPC. So I can provide same answers. * Mike Hearn - OPC is mostly used for data collection, and to a lesser degree to control industrial machines. * Juan Lang AND Robert Shearman - OPC doesn

Re: scroll bars are not shown

I am trying to find the bug and it seems that the size of the given bitmap has no effect at the funktion/visibility of the scrollbars. Can someone give me a hint where the visibilty of the scrollbars is computed? Am 02.09.2004 um 11:59 schrieb Nicolai Kuntze: Can you have a look at the bug #230

EINTR vs. WSAEINTR

Hi list, When calling "select" (or any other socket function, for that purpose), there is a chance that a signal will arrive while we are blocking on the socket. This will cause the blocking function to return with EINTR. The usual recommendation is to retry the operation if that is the case. h

Re: Running valgrind with Wine

Mike Hearn wrote: While we're technically not API stable yet, it's painfully obvious that 1.0 is still a long way away. Stability is a policy rather than a target, so we've got to start at some point I totally agree but that should not stop you from doing things Like: +wine_init_ex( arg

Re: Running valgrind with Wine

Saulius Krasuckas wrote: Possibly, it works. That just I suck: the patch was not applied. :-/ Well, so long as it's working :) Instead I am having trouble compiling the libs/wine dir: loader.c:524: conflicting types for `wine_init' ../../include/wine/library.h:56: previous declaration of `wine_ini

Re: Running valgrind with Wine

On Sun, 5 Sep 2004, Mike McCormack wrote: > Saulius Krasuckas wrote: > > I think i eats all of my RAM and then gets killed by the kernel. I > > guess valgrind wants ~1GB of RAM (or RAM+Swap) while I have only > > 256+300 MBs. > > That's exactly the problem I was trying to fix... it's eating 1Gb o

Re: Running valgrind with Wine

Saulius Krasuckas wrote: Wow, it made some LAAG on my box. I think i eats all of my RAM and then gets killed by the kernel. I guess valgrind wants ~1GB of RAM (or RAM+Swap) while I have only 256+300 MBs. That's exactly the problem I was trying to fix... it's eating 1Gb of RAM because Wine is

Re: Running valgrind with Wine

On Sun, 5 Sep 2004, Mike McCormack wrote: > Saulius Krasuckas wrote: > > Hm, still, for me valgrind doesn't work: > > > > [EMAIL PROTECTED] wine]$ valgrind --tool=memcheck wine-pthread notepad.exe > > Executable range 0x77f0-0x77f02370 is outside the > > acceptable range (nil)-0x52c0 > > v

Re: Running valgrind with Wine

Saulius Krasuckas wrote: Hm, still, for me valgrind doesn't work: [EMAIL PROTECTED] wine]$ valgrind --tool=memcheck wine-pthread notepad.exe Executable range 0x77f0-0x77f02370 is outside the acceptable range (nil)-0x52c0 valgrind: do_exec(/usr/local/bin/wine-pthread) failed: Cannot allocat

Re: Running valgrind with Wine

On Sat, Sep 04 2004, Mike McCormack wrote: > Valgrind stopped working with Wine a while back due to the way Wine > reserves memory above address 0x8000. > > The following patch allows valgrind to work with wine again. You need to > start wine-pthread or wine-kthread instead of starting the win

Re: weird ?clipping? errors

Hi, --- James Hawkins <[EMAIL PROTECTED]> wrote: > me know, because I'm sure this isnt the only program affected by this > bug. The mozilla installers show this as well. Thanks Steven ___ Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! E

Re: Running valgrind with Wine

On Sun, 05 Sep 2004 12:55:33 +0900, Mike McCormack wrote: > -wine_init( argc, argv, error, sizeof(error) ); > +wine_init( argc, argv, error, sizeof(error), reserve ); It's worth noting that any change to this functions prototype breaks the Ardour/Wine VST plugin bridge. Last time this issu

Re: Fix Int21 block device read/write

This should probably be done by querying NT APIs for drive attributes (which ones are those?), http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/base/ioctl_disk_get_drive_geometry.asp A+

Re: fixme:msi:MsiLocateComponentA installing dotnetredist.exe

On Sunday 5 September 2004 07:53, Dan Kegel wrote: > On the console, I saw only the four warnings/errors: >fixme:msi:MsiInstallProductW L"/iH:\\IS3123.tmp\\netfx.msi" L"" >fixme:msi:MSI_OpenDatabaseW open failed r = 80004005! >Installation of /iH:\IS3123.tmp\netfx.msi () failed.

Re: weird ?clipping? errors

James Hawkins wrote: You are correct. What I would like to do is talk to Mike and see what the purpose of the patch is (im sure it does something worthwhile) and then try to fix it so that the clipping problem goes away. The patch fixes a bug in Macromedia Flash MX 6. If you open the "Publish Se

Re: weird ?clipping? errors

> To be more specific, it's this patch: > Mike McCormack <[EMAIL PROTECTED] > > Adjust the tab contents to fix the propsheet between PSM_KILLACTIVE > and PSM_SETACTIVE. You are correct. What I would like to do is talk to Mike and see what the purpose of the patch

Re: weird ?clipping? errors

Filip Navara wrote: James Hawkins wrote: If the error disappears, then you're dealing with a bug in Wine's comctl32.dll. I used native comctl32.dll and both of the errors disappeared, so I will take your advice and search around in comctl32. It's regression in dlls/comctl32/propsheet.c that

Re: Can WINE be made for DOS using GCC for DOS?

Hi, For those interested, I remember there is this thing called 'wdosx' ( http://michael.tippach.bei.t-online.de/wdosx/ ), that is a DOS eXtender containing a stubbed subset of the WIN32 API. From the README.TXT: "Probably the most advanced feature of WDOSX is its emulation of a subset of the