Quote - I just tried it, and the results were unspectacular. The dials disappeared when I deleted the plane (duh), I re-ran the script and all was well. Nothing caught fire or exploded or anything exciting. Ho-hum. :)

Thanks, EB.  :thumbupboth:  Interesting.  In testing, I found that deleting the runner prop (the parameter dials for which are linked to the scene callback) would crash Poser 7 and Poser 8, for all of the loop scripts.  Worse, the "END SCRIPT" dial for the new extrusion script crashed Poser as well.  Yet my old "Make Sphere" script, the first to use the runner prop with callback concept for user input, never caused any crashes at all.

Which, I guess, just illustrates that the scene callback shouldn't be relied upon to handle anything complex.  It can work fine, but it's too easily thrown into disastrous recursion to be trusted with much.  Testing results are inconsistent, presumably, because there are so many factors which can affect the outcome.

I think the new, double-GUI process may be better, ultimately.  It was just a matter of Cage needing to break down and learn how to work with wxPython.  It's not so bad.  Cleaner than Tkinter, and easier in many areas.

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.