visualpython-users

[Visualpython-users] Re: Visualpython-users digest, Vol 1 #736 - 2 msgs

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

----- Original Message -----
> From: Flavio Coelho <fcc...@gm...>
> Hi ,
> I have a PyQT gui that starts a vpython display as part of its functions.
> However, when I close the vpython display it terminates the PyQT as well.
I=
> there a way to avoid this when exiting vpython?

To which J.B. answers:

> From: Jonathan Brandmeyer <jbr...@ea...>
> If you set scene.exit = False, this behavior is supposed to be
> suppressed.
>
> Unfortunately, there is a bug present that keeps this feature from
> working as it should.  It should be fixed soon.

Please advise if this is the same as what I'm experiencing?
I open the Shell, grab a script, run it.  It gives me a stereo (crosseyed)
window and starts showing me my program output (it packs balls; I get to
watch).
When I want to change the conditions, I _used_to_ close the window, make any
changes I want in the script, then run it again.
Now, though, when I close the stereo window, it closes everything and I have
to reload Shell and script in order to run it again.
Is this the _same_ bug as above noted?

Thanks!
(Crosseyed is working *magnificently*, for which implementation I at least
will be forever grateful.
Once I got P2.4 and VP2.4 working on this new machine (AMD Athlon64 3400+;
512MB), everything has been working just as magnificently except for this
above mentioned irritant.)

Peace
JB
Xj...@te...
( REMOVE the 'X' before using ! )
NOTE: due to virus explosion, currently deleting ALL messages over 140kb
from the server without downloading.
http://tetrahedraverse.com

Re: [Visualpython-users] Re: Visualpython-users digest, Vol 1 #736 - 2 msgs

[Bruce S. <Bru...@nc...>]

I'm not sure what is meant by "open the Shell, grab a script." I have 
not seen the behavior you describe except in the following somewhat 
special case, on Windows: Right click on a .py file; choose "Edit with 
IDLE"; run program; close graphics window; everything closes.

But if I start up IDLE (configures either to open a blank edit window or 
the shell window), then open a .py file using File >> Open, then run the 
program, closing the graphics window leaves the other windows open.

Please be more specific about the operations you carry out, and say 
whether the sequence I outlined above works or fails for you. I suppose 
it's just barely possible that there's something odd about AMD. I know 
someone for whom mostly nothing works on AMD.

Bruce Sherwood

John Brawley wrote:

>
>Please advise if this is the same as what I'm experiencing?
>I open the Shell, grab a script, run it.  It gives me a stereo (crosseyed)
>window and starts showing me my program output (it packs balls; I get to
>watch).
>When I want to change the conditions, I _used_to_ close the window, make any
>changes I want in the script, then run it again.
>Now, though, when I close the stereo window, it closes everything and I have
>to reload Shell and script in order to run it again.
>Is this the _same_ bug as above noted?
>
>Thanks!
>(Crosseyed is working *magnificently*, for which implementation I at least
>will be forever grateful.
>Once I got P2.4 and VP2.4 working on this new machine (AMD Athlon64 3400+;
>512MB), everything has been working just as magnificently except for this
>above mentioned irritant.)
>
>Peace
>JB
>Xj...@te...
>( REMOVE the 'X' before using ! )
>NOTE: due to virus explosion, currently deleting ALL messages over 140kb
>from the server without downloading.
>http://tetrahedraverse.com
>
>
>  
>