Maya Restart Script

[doug-hines]

Are there any commands that I can research to create a menu item to restart maya (close application, and restart maya automatically)? I would probably add this command to a userSetup.mel

Thanks.

[joojaa]

QUOTE(kurokawa @ 11/10/07, 11:42 PM) [snapback]276305[/snapback]
Are there any commands that I can research to create a menu item to restart maya ?

Sure, however, theres really no need to do that. Mel scripts and plugins can be re-sourced to force maya to reload them and thus clean any problems that have happened during runtime. Undo can be flushed, drives can be rehashed. So pretty much the only thing you cant flush are global variables. Offocurse your not supposed to use globals in big scale either. And all internal globals will just be reallocated anyway.

So the real question wy would you want to do something stupid like this:

But, just save out the scene, clear maya syystem call maya to reload that scene, and exit.

[doug-hines]

On the off chance that something gets messed up or when I am continuously testing and retesting code changes, this could be quite helpful.

[joojaa]

QUOTE(kurokawa @ 11/12/07, 06:08 AM) [snapback]276344[/snapback]
On the off chance that something gets messed up or when I am continuously testing and retesting code changes, this could be quite helpful.

But thats why you were given the source command.

[doug-hines]

source will not fix incorrectly declared variables in quickly coded test snippets

[joojaa]

Well no but thats why you ALLWAYS put our code inside {} when you type anything in the script editor. Anyway i allready told you how to do this.

Anyway you can just redeclare them inside your {} scope and maya dont then see the ones you made by mistake. Besides you CAN redeclare globals.

[molemansd7]

so is there a way to track down and eliminate random global variables you may have created by mistake?

[joojaa]

Yes, partially if you know their name, buy you shouldn't be making those globals in fisrtplace. . Just dont declare globals unless you really intend to use them if you do use a name thats not likely to clasdh such as mgGlobalVariableWithGoodName. Fixing stuff afterwards is just plain extra. work better.

[ewerybody]

We sometimes have some dirty scenes that mess up the UV Editor. If this occurs the UV Editor will render completely empty grey with only 3 icons showing on the upper left. This way you have to restart Maya as well. I found no solution to fix this with a running Maya. To keep the scene from destroying the UV Editor in the future one has to delete the uiConfigurationScriptNode from the scene and all is cool.

Does anyone else know about this?

[joojaa]

Yes ive seen this and ive seen it fixed... but i dont have a scene thet does this:

Do you have one archived then maybe you can just send the node. Maybe one can the crossref this.

Anway ive taken the habit of disabling all scriptNodes on load, it just saves time as easiest way to break maya is to put something wrong in a script node.

[molemansd7]

QUOTE
Yes, partially if you know their name, buy you shouldn't be making those globals in fisrtplace. . Just dont declare globals unless you really intend to use them if you do use a name thats not likely to clasdh such as mgGlobalVariableWithGoodName. Fixing stuff afterwards is just plain extra. work better.

Are those globals stored in Maya's memory once its closed though? I'm only wondering because last week I was making a lot of scripts, and in the editor, I'd use brackets, but sometimes in my copy and pasting, one would get deleted or something, so a variable would be made global, so I'd restart Maya and it'd be fine. But now for some reason, after I perform random tasks in Maya, it will execute the command fine, but then I'll get a random error saying, "No object exists: " So I think something may be floating around somewhere, but I'm not sure...

[joojaa]

QUOTE(molemansd7 @ 11/13/07, 04:16 PM) [snapback]276432[/snapback]
Are those globals stored in Maya's memory once its closed though?

No, unless you put them inside a load script node. Be very very careful when using script nodes.

Bit for example optionVars are persistent.

[ewerybody]

how do i deactivate onload-scriptNodes?!?

[joojaa]

go to the checkbox next to load and uncheck the option.

[ewerybody]

ah cool! OK I gonna try that!
actually I introduced a function to close annoying windows on sceneload ^^. no need for that now. brilliant!

I'm wondering whats the downside of this... hmm of course UI is not saved anymore. Maybe hurts if I have animation layout defined or any crap... but I guess I wont miss it.

[joojaa]

well it saved, but not necceserily loaded. Besides you can do selective reload later so you can not load eanything and then have ascripjob that ensure the settings were loaded instead. (but nothing else.)