string $allObjects[]=`ls` ;
select -cl;
for($i=0;$i<`size($allObjects)`;$i++)
if(`keyframe -q -keyframeCount $allObjects[$i]` != 0)
select -tgl $allObjects[$i] ;
string $currentPanel=`getPanel -withFocus` ;
string $mode="default" ;
if(`getPanel -to $currentPanel`=="modelPanel")
if(`modelEditor -q -dl $currentPanel`=="default")
$mode="all" ;
modelEditor -edit -dl $mode $currentPanel ;
Very simply, just add "/feeds/posts/default?alt=rss" to the end of your blog address. eg http://ldunham.blogspot.com/feeds/posts/default?alt=rss
Python dictionaries are really, really damn useful in a pipeline. As you store information in a "key: value" type structure, like storing information on a character they repeatedly needs to be called throughout the pipeline, like its rig file path or characterId number. eg "chaInfo={'johnnyId':564,'davidId':565}", so when you call "character['johnnyId']", "564" is returned. Which can then be taken much further... "chaInfo={'johnny':{'num':'cha01','id':546,'file':{'mesh':'johnny_mesh_master.ma','rig':'johnny_rig_master.ma'}}}", so to get the right information you step through them, so for the rig file path you'd call "chaInfo['johnny']['path']['rig']", or the id number "chaInfo['johnny']['id']". So you could have all the information you need regarding an entity or object within a single file, which is very easily called as and when you need it.
Some people have asked about automating the creation of hotkeys as it can be abit fiddly for them to do it manually.
The problem is, like scripting most things, you really need to understand what is actually going on and why.
For example, to automate the creating a hotkey to print what is currently selected.
The script is simply "print (`ls -sl`);"
First of all we need to create a runTimeCommand, which ties the entire script needed to execute under a single runTimeCommand, just like most of maya's own scripts do.
runTimeCommand
-annotation "Prints whatever is currently selected"
-category "User"
-commandLanguage "mel"
-command ("print (`ls -sl`);")
printSelection;
This sets up everything we need to display the command in the hotkeyEditor, without it, you can still assign a command to a hotkey but when your try to find it in the hotkey editor, maya will have no knowledge of it.
Now we need to create a nameCommand which ties the a script to execute under a single string command, just like most of maya's own scripts do.
nameCommand
-annotation "printSelectionNameCommand"
-sourceType "mel"
-command ("printSelection")
printSelectionNameCommand;
Finally we assign a key which runs this command with
hotkey -keyShortcut "~" -name ("printSelectionNameCommand");Now that does seem like alot of work, but it sets up everything you need and with abit of wotk, most of it could be automated, but the things you would need to check and the info you need to enter, theres pretty much no point creating an alternative version of the hotkeyEditor as it requires the same information.
What you could do, however, is to create perhaps hotkey presets, so instead of having to take 3 scripts as you move to a different station (3 being the pref's scripts "userHotkeys.mel", "userNamedCommands.mel" and "userRunTimeCommands.mel"), you could have them those hotkeys into a single custom script which saves its setup as a preset in its own script file.
This could be furthered by doing the same with shelves, window prefs etc, all executed from one script rather than having to transfer the entire prefs folder. Its fairly simple, definitely not the best way of going about it, but its certainly possible.