Luke, Thanks for your help. No hurry on reproducing the bug, at least not on my account. I've seen the light and am going with the method that you and Justin suggested.
- Stuart On Thu, Jul 17, 2008 at 2:46 PM, Luke Crook <[EMAIL PROTECTED]> wrote: > On Thu, 17 Jul 2008 11:41:43 -0700, Stuart Overton > <[EMAIL PROTECTED]> wrote: > > > I hadn't thought of that. I changed my code back to the older version > > that > > used push-quit-event to exit the innermost with-events. When I attempt to > > close the game window, it exits the innermost with-events but not the > > outer. > > I don't know if this helps, but I was originally letting the handling of > > a > > mouse-movement-event call push-quit-event when > > the cursor left a certain area of the screen. I was letting a > > key-down-event > > call push-quit-event as well. > > So what I found is that trying to close the window exits the inner but > > not > > the outer with-events, as does pressing a key, > > This makes sense. The system doesn't know that you are overloading the > SDL_quit event with two different meanings. > > I think what this boils down to is that nesting SDL event loops is not the > correct way to approach this problem. > > > but the handler for mouse-motion-event does seem to generate two > > quit-event > > events, or at least not remove the one it responded to from the event > > queue, > > and this seems to be time sensitive. > > Sounds like this is a bug in the SDL event system, and not so much > lispbuilder-sdl. I'll try reproduce this when I have some time. > > - Luke > _______________________________________________ > application-builder mailing list > [email protected] > http://www.lispniks.com/mailman/listinfo/application-builder >
_______________________________________________ application-builder mailing list [email protected] http://www.lispniks.com/mailman/listinfo/application-builder
