From: Javier G. <xav...@ho...> - 2001-01-31 16:54:04
|
if this helps you, it's what's shown if i do run program, switch-out, switch-in (then crash) warning: sys_switch_in warning: AMNESIA or PAUSE mode recovery warning: mouse_dinput_init warning: clipped updating mode off warning: mouse device was lost warning: sys_switch_out warning: AMNESIA or PAUSE suspension warning: acquire mouse failed = (80070005) warning: sys_switch_in warning: clipped updating mode off and the same when it doesnt crash warning: sys_switch_in warning: AMNESIA or PAUSE mode recovery warning: mouse_dinput_init warning: clipped updating mode off warning: mouse device was lost warning: sys_switch_out warning: AMNESIA or PAUSE suspension warning: acquire mouse failed = (80070005) warning: sys_switch_in warning: clipped updating mode off warning: AMNESIA or PAUSE suspension note the only difference is that the ok one runs AMNESUA or PAUSE suspension after switching in (when it's missed after switch in, it crashes) ----- Original Message ----- From: "Javier González" <xav...@ho...> To: "Allegro Conductors" <con...@ca...> Sent: Tuesday, January 30, 2001 3:51 PM Subject: Re: [AD] [GUI] Error using MSG_IDLE > ok, i applied it over the most recend wddlock.c cvs file > it take a little more switchs to "crash" between its window and the ms-dos > window, but still crashes :( > > ----- Original Message ----- > From: "Eric Botcazou" <ebo...@li...> > To: "Allegro Conductors" <con...@ca...> > Sent: Tuesday, January 30, 2001 2:06 PM > Subject: Re: [AD] [GUI] Error using MSG_IDLE > > > > > Geez. What can I say.... Thnx a lot for all your efforts (cause i don't > > > know even the littlest bit of that file :) > > > > But your little chunk of code is a pretty good test for the locking > > mechanism ! It makes me realize that I weakened the mechanism too much, > > in order to support Henrik's code. Basically, wddlock.c from 3.9.33 is too > > strong for Henrik's code while wddlock.c from 3.9.34 is too weak for > yours. > > > > I hope wddlock.c from 3.9.35 will be nice to both :-) > > I've attached the revised fix. |