Workspace.mel

[gothats]

QUOTE(Joojaa @ 04/29/03, 12:56 AM) [snapback]146770[/snapback]
workspace. mel wich contains the directory structure settings is just sourced on project change and starup! what this essentialy means is that you can actualy put soem mel code to build codes that are initialized in that project only!

I saw this post in the scripters tips, but I can't get it to work.

I tried putting some mel code into the workspace.mel file, and it didn't seem to do anything. It should be able to execute any command, right? I tried a print statement because I thought that would be simple enough, and when it didn't print the string that I entered, I put a "sphere" command, which also didn't work.

I have this:
CODE
//Maya 7.0.1 Project Definition

workspace -ot "scene" "scenes";
workspace -fr "OBJexport" "data";
workspace -fr "OBJ" "data";
workspace -fr "particles" "particles";
workspace -rt "sourceImages" "sourceimages";
workspace -rt "textures" "textures";
workspace -rt "images" "images";
string $myCustomString = "It works";
print($myCustomString);

But when I load that project, "It works" is not spit out to the command line. Is this stuff cached? Does maya have to be restarted to make changes to the workspace.mel file? I tried that, which also didn't work...

Ultimately I want to be able to set different hotkeys and marking menus based on the current project. Is this possible?

[naughty]

try evalDeferring it:

CODE
//Maya 7.0.1 Project Definition

workspace -ot "scene" "scenes";
workspace -fr "OBJexport" "data";
workspace -fr "OBJ" "data";
workspace -fr "particles" "particles";
workspace -rt "sourceImages" "sourceimages";
workspace -rt "textures" "textures";
workspace -rt "images" "images";

string $myCustomString = "It works\n";
evalDeferred("print \""+$myCustomString+"\"");

rather than place all the commands in the workspace.mel file like this, it'd be better to evalDefer a single script proc that executes all the command you want to run at startup (in case you hadn't thought of that already! )...

:nathaN

[joojaa]

Its run before most of the gui is loaded try making a error in the file and youll see it quite clearly as you get the error in the output window. What happens is mayas running it so early you have no chance to see it. The sphere isnt created because maya news the scene as last thing on init. See http://www.highend3d.com/boards/index.php?showtopic=230523 which is the last post to cover this aspect of maya.

Anyway maya sure runs this piece of code. try putting this into your workspace.mel

scriptJob -event "deleteAll" "sphere";
evalDeferred("print \"Hey\"");

And suddenly all you do is there

[gothats]

The evalDeferred seems to be working, but I'm having a strange problem with strings...

If I say:
print "Hi\n";
It works just fine. Hi is printed and a newline.

But if I say:
evalDeferred("print \"Hi\n\"");
I get an error:
// Error: print "Hi //
// Error: Unterminated string. //

If I take the "\n" out, it works, if I use a different nonprinting character like "\t" it works, anything except "\n". This seems like a really stupid problem. Do I just have the wrong syntax?

----Found it-----
It should be
evalDeferred("print \"Hi\n\"");
The "\" in "\n" has to be escaped, so it becomes "\n".

[user_deleted]

Hi all !

I too used workspace.mel to setup some my tools on project basis, but i had quite different problem. From time to time, the script was overwritten by default one, probably by maya running on someone else's machine... what goes ? Maybe there's onother way to make maya do smth on project change ? Maybe nice thing would be an autoSource directory in project ? Every .mel file would be sourced on project change...

-michal

[joojaa]

Yes, see the workspace mel is generated by the set workspace command. So if somebody changes the workspace settings itll get overwritten.

To this end ive changed the approach a bit what i do is put a source projectSetup
in one of the always sourced files. then what i just do is add a mel directory to all my project spaces and add the default changes in projectSetup instead. (i also have a projectUnsetup thet gets called on project change along with a rehash the and next projectSetup)

A alternate is to wirteprotect workspace