Re: make system brushes, pens non-deletable
At 06:46 PM 9/12/00 -0500, you wrote: Hmm, we had some more discussion about that system object deletion, and Alexandre told me that we can't accept extra DLL exports (we have to remain compatible in case different software packages want to use one libgdi32.so) How about using GetProcAddress ? Gerard
Re: make system brushes, pens non-deletable
On Wed, Sep 13, 2000 at 01:36:06AM -0500, gerard patel wrote: At 06:46 PM 9/12/00 -0500, you wrote: Hmm, we had some more discussion about that system object deletion, and Alexandre told me that we can't accept extra DLL exports (we have to remain compatible in case different software packages want to use one libgdi32.so) How about using GetProcAddress ? Yes, of course you could do that. I'm not sure what to do. He wants to flip the flags in memory in USER. That's probably a better idea, even though it's a bit ugly (calculating memory offsets and such). But Windows isn't "clean" either... We pretty much have agreed on that. I'll send a patch later today. Andreas Mohr
Re: make system brushes, pens non-deletable
At 03:40 PM 9/12/00 +, you wrote: Hi all, this patch lets Wine know about non-deletable system brushes and pens created by USER. (see WD mail Gerard Patel subject "seeking advice on fixing deletion of system brushes") If you have any issues with the naming of the define MAGIC, then just tell me. This is done the way Windows seems to flag its GDI objects, BTW. (binary compatible :) I remember dimly having seen posts about using native Gdi, does anyone know if this is still theoretically possible ? Gerard
Re: make system brushes, pens non-deletable
Gerard Patel wrote: I remember dimly having seen posts about using native Gdi, does anyone know if this is still theoretically possible ? Well, everything is possible :-/ Unfortunately, even native User doesn't work anymore; because of address space separation, it didn't work with 32-bit apps any longer, and now it doesn't even work with 16-bit apps because recently KEYBOARD/MOUSE/DISPLAY have been folded back into USER ... So, we'd have to: - move KEYBOARD/MOUSE/DISPLAY out of USER again - get -desktop working again - try whether USER works for 16-bit and fix potential bugs - find some clever solution (that currently I don't see) to get USER running for 32-bit again - probably even so it won't work for multiple 32-bit apps at the same time, because 16-bit segments are no longer shared (maybe use some hack that optionally moves 16-bit segments into a shared heap; I can guess that Alexandre won't like this however ;-) For GDI, we'd have in addtion to: - implement a proper DISPLAY driver to actually see any output Bye, Ulrich -- Dr. Ulrich Weigand [EMAIL PROTECTED]
