Alex Bennee wrote: > On Mon, Feb 2, 2009 at 5:04 PM, Andrew Straw <astraw@xxxxxxxxxxx> wrote: > >> Alex Bennee wrote: >> >>> Hi, >>> >>> I'm doing some work on an experiment for a friend of mine. It's my >>> first time using VisionEgg and I'm having problems with correctly >>> clearing down the session. If my experiment bails out the Vision Egg >>> window stays displayed. It's then random if the next time I run the >>> experiment if it will fail to start (example: "error: Text has zero >>> width") or crash python completely. >>> >>> I'm running this on WinXP which is a little outside of my natural >>> environment so I'm not sure if this is a Windows thing or a VE thing. >>> >>> >> Hi Alex, >> >> I don't think I've experienced this before, but I'm not entirely clear >> what's happening. If you run your script from the command line, does the >> first script quit entirely (you get a prompt back) before running the >> second? >> > > It's running in the python shell (via emacs). So it never quits python > fully (emacs keeps the inferior python shell running as long as > needed). > > >> Did the first script close properly, or did an exception happen? >> > > It threw an exception in my code and dropped back to the python -i shell. > > >> If an exception, can you cut and paste that exception? >> > > I could (if I was at the machine right now :-) but the exception is in > my code so it's probably not relevant. However the VisionEgg GL window > stays open. I tried myApp.screen.close() but that didn't seem to help. > You could try pygame.quit(). Other than that, my other suggestion is to kill the VE process via the operating system. -- Dr. Andrew D. Straw California Institute of Technology http://www.its.caltech.edu/~astraw/ ====================================== The Vision Egg mailing list Archives: //www.freelists.org/archives/visionegg Website: http://www.visionegg.org/mailinglist.html