Scriptjob On Save

[quitter]

Hi everyone,

I'm trying to execute a scriptjob on scene save, but it doesn't look like that's a valid scriptjob event. From reading the past posts here, it looks like there's just no supported event that can be used by the scriptjob command. Can anyone confirm this, or give me a suggestion on how to execute actions on scene save? Thx in advance.

[failure]

What actions do you want do execute?

[joojaa]

Try using a scriptNode! Anyway what do you need it for. Since you can easlily overload saving protocolls. As well as making sure the sytem does this for you.

[ewerybody]

hmm we were looking for something like this too :[
I haven't found anything. And the scriptnode seems to be not able to do the Job either.

Since we have a proprietary save-dialog we can do stuff there. But if people use Ctrl-S no chance anyway ;]

[joojaa]

Yes you can override the menuitem, And evnbody your joking right

QUOTE(ewerybody @ 07/13/06, 03:15 PM) [snapback]242351[/snapback]
Since we have a proprietary save-dialog we can do stuff there. But if people use Ctrl-S no chance anyway ;]

Well thats actualy easily solved! The only thing you CANT protect* yourself is people typing the save command from a script. BUT that should be ok since IF you change thsi then you will get random breaking in the sytem anyway.

The fix is
CODE
global proc SaveScene(){print "Dont use ctrl-S\n";}

Offcourse you can populate this with a handle to yoru way of doing this. OR a more elegant way is to do a copy of

defaultRunTimeCommands.mel

And put it on a higher priority scriptfolder and edit the SaveScene runtimes definition in the same way. Now you can have wahtever even on the ctrl-S too. They are just named versions.

Anyway redirecting the menuitem and ctrl-s realy does this potection as well as anybody will ever want to do it, because iotherwise ts more of a development hinder than anything else.

• Well actualy you can, all you need to do a api command that exactly mimics save but add your own hook there, offcourse its easier to expose a event anyway. But this isnt foolproof since anybody knowing mel can allways switch it off. This leads to the bottomline you can ALLWAYS circumvent EVERYTHING any developper does in maya, OTHER than maya core developpers (good thing too means that i can disenfect all maya macroviruses). So everything you do i can counter! So no ENCRYPTED maya files, hell i can even rob data from PLE to normal maya and back without much fuzz, the no file writing is just more of a annyoance here than a hinder. Hell i think i can even write out files form ple with a bit of trickery in older ples (they have fixed this in .0).

[failure]

I always wondered why do people need stuff like this. Because it sounds like playing cheap trickery on innocent users. The point is - if you want to do something irregular you put it into irregular command and let the user trrigers it by executing that irregular command. And make very obvious for user that he/she is doing it. You don't hijack regular, everyday, well-behaved, good-old commands like save as. Not decent. No, no.

[quitter]

Thanks for all the responses.

On save I'm trying to write information about the file into a database. I don't want to use a scriptnode because that's per-file and I don't want to add excess nodes to everyone's files all the time.

I want to seamlessly assure that the data save in the file is the same as the data in the database. From all your comments it looks like I need to go to the API to do this.

[ewerybody]

Well the thing here was that all the artists that ... as the name says are artists and no maya-scene clean keepers. So one thing is they open every window that can be opened in Maya, minimize it and save the scene. Now there are about 16 windows that can be saved with the scene, and if now someone else opens up the scene (e.g. the art directior) all the windows popup at once and you are busy clicking away those windows instead of viewing the object...

I already set up a killFloatingWindowsOnLoad scriptJob but at scene safe is harder of course
But I guess yet with a scriptjob like this the floating window madness will be less and less..

[joojaa]

QUOTE(rasengan @ 07/13/06, 09:03 PM) [snapback]242381[/snapback]
I want to seamlessly assure that the data save in the file is the same as the data in the database. From all your comments it looks like I need to go to the API to do this.

Nobody said that. Anyway we object actualy making modifications like thiui to maya bacuse it HURTS the user. All you do is you override:

SaveScene, (evenbody shoul have known this having a problem witha shortcut is as ridiculous as saying fish need bicycles), like above jut put some action to this. This overrides a person pressing ctrl-S, aswell as any actions taken by file -> save scene.

SaveSceneAs. this overrides the file-> save Scene as...

And possibly if you need the options sanely:

SaveSceneOptions
SaveSceneAsOptions

This takes care of EVERYTHING except using save form commandline, or script so normal users are safe by that. However you will not want to override those script saves API OR NOAPI, because the user of those scripts MAY use those saves as means to get into a maya ascii code of somekind or embed MI code (and want maya to parse it out). THis also incidentaly BREAKS svreal factoruyscripts form working 100%properly such as calling batch render (no biggie this offcourse goes to your renderfarm). Anyway telling td to avid sonething because of this and that iis better because otherwise they build cludge on cludge to avoid it. Bavcuse quite frankly they will get around it no matter what you do excluding shooting them in the head.

You may want to also override following

Export;
ExportSelection;
corresponding options.
hyperShadePanelMenuCommand("hyperShadePanel1", "exportSelectedNetwork");

However what ID do i let the operating sytem chek for this (it has a sevice for this youknow). And yes i do use cvs for saves, as well as drop in folders. Works fine . As for going into api we-el you can do that but you automaticaly break alot of safety features in your maya. And its not simpler. All i said was if you are one of those pedantic people who think in line i must be 100% sure then to your dismay i will say ITS NOT. the api solution isnt any safer than overriding.

Note that from apis point of view export is the same as save as! An yes by the way ive had this discussion about 20 times ive tested their way see it break and gone back to mine

[quitter]

I see, thanks for the clarification! I appreciate the help, and I'll try what you've suggested (overriding the save MEL functions).

[failure]

QUOTE
I'm trying to write information about the file into a database

I really can't see point in doing this, especially not from within maya. I mean when you save a scene the information is saved. Your project directory is your database. And if you need it in other database just scan the project directory and transfer everything you need into database. If you want to record every save operation (which is even more pointless) then use incremental save.

If you absolutely must track everyhing - that's the OS's business. So as already said it's either OS level thing or CVS (I vote for CVS option). Overriding the save command in maya is the stupidest approach to this problem. You don't deal with this kind of things from within application because they are ulimately corruptable from outside of it. What if you store something in database on save as and someone delete the file from shell? Not a good way to track.

QUOTE
artists and no maya-scene clean keepers

Every artist is he's own scene clean keeper. Besides you are mixing the terms a bit. The fact that painter's desk (interface) is untidy doesn't mean that he's painting (scene) will be untidy too.
If someone wants to have 16 floaters saved with scene - that's his problem. Maybe he's on dual display or something. So best place to handle this is right where you said - on load on your system because it annoys you, not on save on somebody else's system.