Okay, I've thought about how to make the wine kernel module easier to use for
Wine, and I've started adding another API to it - one that interprets Wine
server messages. When I designed the module initially, I decided to make it
possible to add as many API's as I liked, so in theory it's not too
and (B) should we support MS's hack somehow in the official tree?
Yes, in the Wine debugger, which should store the name and simply
continue execution, just like the MSVC debugger does.
OK, I don't know too much about the internals of the WINE debugger, so
here goes. Is there a field for
Hi,
I have a 3rd party x86 DLL file, that I would like to use under Linux. I
have read the documentation on the specmaker tool, which would seem to
provide some help. The thing that makes my case a bit different is that I
would like to use the DLL within a Linux native program, not a WineLib
"James Hatheway" [EMAIL PROTECTED] writes:
OK, I don't know too much about the internals of the WINE debugger, so
here goes. Is there a field for this already, or should I make a new
field in DBG_THREAD structure? (I think that seems like the right place
for it)
Yep, you can add a field
Dmitry Timoshkov wrote:
Sure. -debugmsg +??? serves for finding problems too, doesn't it? FIXME tells
about not complete implementation, in the case of psdrv - about missing page
and bin type.
Is it really appropriate to spit out a FIXME every time we encounter a
paper size or bin type that
"Ian Pilcher" [EMAIL PROTECTED] wrote:
Is it really appropriate to spit out a FIXME every time we encounter a
paper size or bin type that we don't recognize?
I would agree with you, if you have added all regular possible values listed
in wine/include/wingdi.h and only then replaced FIXME's by
