tromnek opened this issue on Nov 23, 2005 ยท 44 posts
layingback posted Thu, 24 November 2005 at 11:11 AM
Re auto loading: Another problem with autoloading using PoserStartup.py is that the poser script has to run for the whole time that your Poser app is running. Due to the way poserStartup itself is called, there is no way to safely end the loaded routine, as the routine you loaded is essentially Poser to the OS, so anything you do to it - like closing it - impacts Poser too. You can fudge it so it doesn't actually kill the Poser task, but that results in a modal dialogue box coming up with a serious sounding error message, which you have to manually close to allow Poser to proceed. Not elegant. So until/unless CL/EF change the way poserStartup.py itself is called (to spawn rather than start it?) using poserStartup.py to load an external rountine is a no-no.