@Larry,

re:
> Interesting idea. I haven't had cause to tinker with the startup scripts, but could imagine there
> is a use-case for allowing an ordering mechanism. Might be a bit interesting to make it
> generalized though: would users have to either edit that first line or perhaps rename files,
> either way seems to make it more challenging to support.

It wouldn't be something for users to edit really, it would be for the author of the script to use when making the script. Like maybe some script that wants to totally replace the UI would work more smoothly if it ran early on in the startup process so it wouldn't need to load the regular UI and then throw it away. While some other script that wanted to make a minor modification to the UI would work better if the regular UI was all finished being set up.

Some other possibilities might be that it could say "run after a file is loaded", "run before shutdown", stuff like that.

At any rate, it was intended that the current startup scripts should run after the UI is set up but right before the window is actually displayed, so that they could modify things without stuff visibly shifting or flickering on screen. But while trying to do this script over here: http://moi3d.com/forum/messages.php?webtag=MOI&msg=6925.554 I discovered that they were running a little earlier than I thought (at least on Windows), it was happening after the UI content was finished loading but before the main window had been sized. It's a little difficult for a script to modify some elements of the UI at that point with other parts of the startup process like the initial UI panel layout still coming after that.

It also appears that with the previous way there was some difference in the state of the app between Windows and Mac at the time the startup scripts ran so that's not good. I need to look at this a little more to make sure.

- Michael