How to integrate user-defined SaveScene() into Maya?

[yao-yansi]

Hi all,
I’m going to integrate a user-defined SaveScene() routine into Maya2009.
I think I have to replace the following 3 commands in Maya:
1.the command of the “Save Scene” MenuItem in “File"Menu,
2.the command of the SaveScene icon,
3.the command of the “Ctrl+S” short cut.

My questions are:
1.If the source mel scripts of Maya2009 can’t be modified, how can I register my SaveScene() to Maya to replace the original save scene routine?
I know how to replace the command of the “Save Scene” MenuItem. Here is the answer(http://nccastaff.bournemouth.ac.uk/jmacey/RobTheBloke/www/research/maya/version\_control.htm). But the problem is even I replace the command of the "Save Scene" MenuItem by mySaveScene(), like this:
     global proc mySaveScene() {
        //.....
     }
     menuItem -e -c "mySaveScene" "saveItem";
mySaveScene() is still can't be executed when I press the SaveScene icon or use "Ctrl+S".

2.If the source mel scripts of Maya2009 can be modified, how can I register my SaveScene() to Maya to replace the original save scene routine?

And I prefer the first solution if it is possible.

Thank you.

[joojaa]

I think I have to replace the following 3 commands in Maya:

No just define a new global porc SaveScene in mel.

2.If the source mel scripts of Maya2009 can be modified,
  how can I register my SaveScene() to Maya to replace the original save scene routine?

just run the proc into memory. Last run procedure definition overwrites the old one and thus takes precedence. So if you run:

global proc SaveScene(){
  print "yeah well im not allowing you to save anything trough the GUI";
}

Now you MAY actually want to redefine SaveSceneAs too:

global proc SaveSceneAs(){
  print "yeah well im STILL not allowing you to save anything trough the GUI";
}

Thats it. So just put them in any file and make sure that file gets sourced in user prefs as deferred. Or indeed at any time you want to take over the default procs.

OR
since SaveScene is a run time command just redefine the runtime command to point somewhere else. This allows you to do minimal developent as you could just append the functionality you need.

[yao-yansi]

Thanks for your reply, Joojaa,
But the problem is even I replace the command of the "Save Scene" MenuItem by mySaveScene(), like this:

global proc mySaveScene() {
    //.....
}
menuItem -e -c "mySaveScene" "saveItem";

mySaveScene() is still can't be executed when I press the SaveScene icon or use "Ctrl+S".

since SaveScene is a run time command just redefine the runtime command to point somewhere else. This allows you to do minimal developent as you could just append the functionality you need.

But it complains:
 // Error: Not allowed to change command of a default run time command. //
When I run this code:

global proc mySaveScene()
{
    print("-------mySaveScene()--------");
    //.....
}
runTimeCommand -e -command    ("mySaveScene()")   SaveScene;  //replace original SaveScene() by mymySaveScene()

It seems that the runtime command can't be changed at run time.

[yao-yansi]

just run the proc into memory. Last run procedure definition overwrites the old one and thus takes precedence.

Yes, you are right. Finally, I decide to overwirte the original SaveScene() at runtime.

[joojaa]

procedures teka precedence over runtime commands yes.