Re: ddraw: make some driver info not const

2005-12-05 Thread Rein Klazes
On Mon, 05 Dec 2005 12:07:32 +0100, you wrote: > >You can't return from inside a __TRY block. I did not know. Here is the next attempt: Changelog: dlls/ddraw : main.c, Makefile.in Catch access violations when calling the DirectDrawEnumerateProc. Rein. --- wine/dlls/ddraw/main.c 2005-

Re: ddraw: make some driver info not const

2005-12-05 Thread Alexandre Julliard
Rein Klazes <[EMAIL PROTECTED]> writes: > +__TRY > +{ > if (!lpCallback((DDRAW_default_driver == i) ? NULL > :(LPGUID)&DDRAW_drivers[i]->info->guidDeviceIdentifier, > (LPSTR)DDRAW_drivers[i]->info->szDescription, >

Re: ddraw: make some driver info not const

2005-12-04 Thread Rein Klazes
On Sat, 3 Dec 2005 09:44:07 +0100, you wrote: >> This is wrong. No user program should modify our internal data. I think >> you need to copy this data into heap before passing it to the app. You >> should make simple test to check if the data returned on windows is >> within heap or not. > >Yeah,

Re: ddraw: make some driver info not const

2005-12-03 Thread Lionel Ulmer
On Fri, Dec 02, 2005 at 12:11:34PM -0700, Vitaliy Margolen wrote: > Friday, December 2, 2005, 11:46:39 AM, Rein Klazes wrote: > > Hi, > [skip] > > Making this information not const makes the application proceed further. > > > Changelog: > > dlls/ddraw : ddraw_hal.c, ddraw_user.c > > Make some dri

Re: ddraw: make some driver info not const

2005-12-02 Thread Vitaliy Margolen
Friday, December 2, 2005, 11:46:39 AM, Rein Klazes wrote: > Hi, [skip] > Making this information not const makes the application proceed further. > Changelog: > dlls/ddraw: ddraw_hal.c, ddraw_user.c > Make some driver info not const, some applications want to modify it. This is wrong. No user