Re: [Visualpython-users] Re: horror story

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

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.

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.

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.

Bruce Sherwood

John Brawley wrote:

>>   1. Re: Horror story (Jonathan Brandmeyer)
>>From: Jonathan Brandmeyer <jbr...@ea...>
>>    
>>
>[deletions]
>
>  
>
>>I think that it means that you were somehow creating an visual object
>>with an explicit color value set to "None" rather than a 3-tuple.
>>    
>>
>
>That's really odd, since I don't.  (*grin*)  What I'm doing is using an HSV
>color 3-tuple, since I only have to work with one element (the H, the first
>in the 3-tuple) in order to get a full range of colors according to a
>certain property of the object.  I then just translate the HSV to RGB for
>VPython's use.  Even if the first element of the tuple were weird, the other
>two elements are explicitly 1 and 1 (hue, 1,1).
>
>  
>
>>You can add an extra couple of lines of code to
>>process_init_args_from_keyword_dictionary (in primitives.py) that tests
>>keywords for the 'color' key and prints out the value if it exists.
>>eg,
>>if 'color' in keywords:
>>print type(keywords['color']), keywords['color']
>>    
>>
>
>Thank you, Jonathan, I'll try that, but I can't print anything to the shell
>window; I'll have to try to write any messages to a file and even that
>is unlikely to work.  When the program runs and expecially when this
>happens, the program hogs focus and the CPU is in 100% usage.  I can't even
>Windows-multitask at all and that's on a 2.2 GHz (Intel 3.4 GHz equivalent)
>Athlon64 w/512 MB memory.
>Thus I can't _see_ the shell without minimizing the stereo window, which
>sometimes works (after a _long_ pause) and sometimes doesn't.  There's
>no chance of catching "live" error messages, or more than one of them
>if static.
>
>This is all because the scene.exit=0 function (close the stereo window;
>leave the shell and edit windows open) _doesn't work_ in this VPython (2.4).
>I wanted especially to know if that has been fixed.
>Has it?
>(I know there's a new version up, but has this particular irritant been
>fixed in it?  I can't go on forever re-initializing Idle every time I close
>the stereo window.  It makes it really hard to work on a program when I have
>to start from scratch every time I test some minor thing and have to close
>the stereo window....)
>
>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
>  
>