Folding the low-level DirectInput functionality into the drivers (probably
along the lines of the DirectInput DDK), like I did with DirectSound (if
we ignore the bad job I did with Half-Life compatibility), make a lot of
sense (although I originally thought the joystick driver would benefit
Andreas Mohr [EMAIL PROTECTED] writes:
Alexandre: please check whether all other occurrences of
ConvertToGlobalHandle() are still legitimate !
(I think so, but not sure)
AFAICS they should all be removed except for the one in
MakeCriticalSectionGlobal.
--
Alexandre Julliard
[EMAIL
"Dmitry Timoshkov" [EMAIL PROTECTED] writes:
Changelog:
Small correction for path stripping.
This breaks paths that contain both '/' and '\'. What are you trying
to fix?
--
Alexandre Julliard
[EMAIL PROTECTED]
Hi all,
more verbose error message.
(not just say that something fails, but also WHAT to do...)
Andreas Mohr
Index: scheduler/client.c
===
RCS file: /home/wine/wine/scheduler/client.c,v
retrieving revision 1.52
diff -u -r1.52
Does WINE have to be in a directory on a FAT
partion?
Everytime I ran something that caused the Wine to
kick off the Wine Debugger, it would 'die' with an
error message saying it wasn't on a FAT drive or
something like that.
Thanks
George
__
On Sat, 26 Aug 2000, gerard patel wrote:
I sent the following patch last week to wine-patch and it was committed
2 days ago or so. Btw, only horribly flawed programs have a problem
here
;-)
Oh Ho! I was seeing traces where the same call with the same
parameters succeeded before. That
Good day!
This used to work. As near as I can make out, it now (wINE-2821)
fails in GDI_GetObjPtr(dc-w.hBitmap, BITMAP_MAGIC), where w.hBitmap is
hPseudoStockBitmap, called by X11DRV_CreateDC. I can't see why anything
that has changed should sabotage this.
I still can't get winedbg to
