On Sun, 2005-01-23 at 22:33 -0500, Gregory Pittman wrote: > It doesn't work properly and actually is less useful from within Scribus > -- I was hoping the list it generates would just hang there and you > could continue using Scribus, but use of Scribus is suspended while the > list is there; also it hangs and won't shut off properly from within > Scribus. Maybe I'll figure that out later.
Scribus is single-threaded. When it runs a script, it waits for the scirpt to exit before continuing. The interpreter the script runs in is destroyed when the script exits. Because of this you can't create GUI objects then continue to use scribus. ... however, if/when my macro work is merged, it'll be possible load scripts that don't have their interpreters destroyed when they exit. This means that PyQt windows, at least, can be created and continue to exist while the user does other things. I'm not sure about Tkinter and Gtk yet ... need to look into how the event loops interact with Qt's. -- Craig Ringer
