Menu
▾
▴
visualpython-users
|
From: John B. <jb...@te...> - 2005-12-08 14:16:46
|
> From: Bruce Sherwood <Bru...@nc...> > Subject: Re: [Visualpython-users] Re: horror story > > On the exit issue: This is two different issues, not one. With the > Boost-based version of Visual there crept in a new bug that scene.exit = > 0 doesn't prevent the exiting of all graphics wndows when one is closed. > That has not yet been fixed. Thanks. That is sad. (You do mean, don't you, that scene.exit=0 doesn't prevent exiting of all _VPython_ windows, not just graphics windows? My experience: closing the graphics window (my old three-window stereo method's, _or_ the single window given by scene.stereo='crosseyed'), shuts that window, Idle (shell) window, and the program edit window. IOW, _everything_ closes and I have to start all the way over as if I had just turned on the computer.) Is it important to fix this? (Are there a lot of complaints about it, or not?) > But there's a different issue that has always been present as far as I > know, and never understood. If you start IDLE, then open a file for > editing, you can repeatedly run, close the graphics window, and keep > editing. _Yes_. That's what I was familiar with, which makes it easy/fast to work on a program, test, do more work, test, etc. That's the way (imho) it _should_ be. > If on the other hand (on Windows) you right-click on a .py file and ask > to edit using IDLE, you only get to run once before IDLE itself quits, > which is annoying. But starting from IDLE gets around this problem. I've never seen that, because I don't start Idle that way, but always from a desktop icon/shortcut. (IOW yes, I always start from Idle.) Peace JB jb...@te... Web: http://tetrahedraverse.com |
|
From: Bruce S. <Bru...@nc...> - 2005-12-08 14:52:39
|
What you're seeing has not been reported by anyone else. As far as I know, you're the only user experiencing the disastrous behavior you report, that starting from IDLE you can run only once before everything closes down. This has nothing to do with the scene.exit bug, which everyone experiences (if they use that not very commonly used feature). The uniqueness of your experience suggests something odd about your particular computer environment, but I have no idea what the problem is. One thing you might try, in desperation, is to uninstall VPython, then uninstall Python, then reinstall. Bruce Sherwood John Brawley wrote: >>From: Bruce Sherwood <Bru...@nc...> >>Subject: Re: [Visualpython-users] Re: horror story >> >>On the exit issue: This is two different issues, not one. With the >>Boost-based version of Visual there crept in a new bug that scene.exit = >>0 doesn't prevent the exiting of all graphics wndows when one is closed. >>That has not yet been fixed. >> >> > >Thanks. That is sad. >(You do mean, don't you, that scene.exit=0 doesn't prevent exiting of all >_VPython_ windows, not just graphics windows? >My experience: closing the graphics window (my old three-window stereo >method's, _or_ the single window given by scene.stereo='crosseyed'), shuts >that window, Idle (shell) window, and the program edit window. IOW, >_everything_ closes and I have to start all the way over as if I had just >turned on the computer.) > >Is it important to fix this? >(Are there a lot of complaints about it, or not?) > > > >>But there's a different issue that has always been present as far as I >>know, and never understood. If you start IDLE, then open a file for >>editing, you can repeatedly run, close the graphics window, and keep >>editing. >> >> > >_Yes_. That's what I was familiar with, which makes it easy/fast to work on >a program, test, do more work, test, etc. >That's the way (imho) it _should_ be. > > > >>If on the other hand (on Windows) you right-click on a .py file and ask >>to edit using IDLE, you only get to run once before IDLE itself quits, >>which is annoying. But starting from IDLE gets around this problem. >> >> > >I've never seen that, because I don't start Idle that way, but always from a >desktop icon/shortcut. >(IOW yes, I always start from Idle.) > >Peace >JB >jb...@te... >Web: http://tetrahedraverse.com > > > > >------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. Do you grep through log files >for problems? Stop! Download the new AJAX search engine that makes >searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >_______________________________________________ >Visualpython-users mailing list >Vis...@li... >https://lists.sourceforge.net/lists/listinfo/visualpython-users > > |
|
From: Jacob S. <ke...@ja...> - 2005-12-08 21:14:22
|
> What you're seeing has not been reported by anyone else. As far as I know, > you're the only user experiencing the disastrous behavior you report, that > starting from IDLE you can run only once before everything closes down. > This has nothing to do with the scene.exit bug, which everyone experiences > (if they use that not very commonly used feature). > > The uniqueness of your experience suggests something odd about your > particular computer environment, but I have no idea what the problem is. > One thing you might try, in desperation, is to uninstall VPython, then > uninstall Python, then reinstall. > > Bruce Sherwood You're not alone John, I have experienced this problem before. I tend to edit with idle, then Alt+Tab to the open folder and hit enter on the file I'm editing. This way I can edit, save, alt+tab, enter - it runs, alt+tab, edit, etc. Jacob Schmidt PS Running Windows XP, -and- I don't know if this helps but - the file association on edit with idle is as follows "C:\python24\pythonw.exe" "c:\python24\lib\idlelib\idle.pyw" -n -e "%1" %* The file association might affect how idle interacts, say, whether it shuts down or not... If idle thinks that -n or -e is a call to shut down after running (it's a shot in the dark) HTH > > John Brawley wrote: > >>>From: Bruce Sherwood <Bru...@nc...> >>>Subject: Re: [Visualpython-users] Re: horror story >>> >>>On the exit issue: This is two different issues, not one. With the >>>Boost-based version of Visual there crept in a new bug that scene.exit = >>>0 doesn't prevent the exiting of all graphics wndows when one is closed. >>>That has not yet been fixed. >>> >> >>Thanks. That is sad. >>(You do mean, don't you, that scene.exit=0 doesn't prevent exiting of all >>_VPython_ windows, not just graphics windows? >>My experience: closing the graphics window (my old three-window stereo >>method's, _or_ the single window given by scene.stereo='crosseyed'), shuts >>that window, Idle (shell) window, and the program edit window. IOW, >>_everything_ closes and I have to start all the way over as if I had just >>turned on the computer.) >> >>Is it important to fix this? >>(Are there a lot of complaints about it, or not?) >> >> >>>But there's a different issue that has always been present as far as I >>>know, and never understood. If you start IDLE, then open a file for >>>editing, you can repeatedly run, close the graphics window, and keep >>>editing. >>> >> >>_Yes_. That's what I was familiar with, which makes it easy/fast to work >>on >>a program, test, do more work, test, etc. >>That's the way (imho) it _should_ be. >> >> >>>If on the other hand (on Windows) you right-click on a .py file and ask >>>to edit using IDLE, you only get to run once before IDLE itself quits, >>>which is annoying. But starting from IDLE gets around this problem. >>> >> >>I've never seen that, because I don't start Idle that way, but always from >>a >>desktop icon/shortcut. >>(IOW yes, I always start from Idle.) >> >>Peace >>JB >>jb...@te... >>Web: http://tetrahedraverse.com >> >> >> >> >>------------------------------------------------------- >>This SF.net email is sponsored by: Splunk Inc. Do you grep through log >>files >>for problems? Stop! Download the new AJAX search engine that makes >>searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >>_______________________________________________ >>Visualpython-users mailing list >>Vis...@li... >>https://lists.sourceforge.net/lists/listinfo/visualpython-users >> > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X