[Visualpython-users] Re: scene.exit=0

[John B. <jb...@te...>]

> 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