hi phuong ,

thanx for your comment ... well, it is just bad luck for me , that 
usually does not happen , and it is really embarassing

i guess it will be just 2 hours of "re-work" , but right now i was a bit 
fed-up ( hehe ) ... this time it will be much faster , as i already 
"found" out each of the neccessary "Rigging-Steps" in order to add some 
new funcionallity to my Rigging

right now i implent some elbow-Locking .... break-up the existing 
auto-rig ... add nodes and bones and constraints ... then re-connect 
everything . i hope i get it done this evening , to concentrate on some 
other work tomorrow .

thanx for the suggestion with the "scriptEditorInfo"-command - i guess i 
will not use it , but it would be great , if maya would backup the 
scripts by its own . you see in maya 2008 they added this 
"Multi-tab"-editors and also search-and-replace-function ... but did not 
implent a simple backup-scripts-folder ( in case of a maya-crash )

but it is my mistake , i know it ... and every year it happens once

anyway , have a great week ( you all )

sim.On


ngohoai.phuong schrieb:
> Hi all,
> You can put command scriptEditorInfo save to text file before write a
> script in MEL or PYTHON.
> thanks,
>
> On 4 Tháng Mười, 20:21, "sim.On" <[EMAIL PROTECTED]> wrote:
>   
>> hi Python users .
>>
>> i guess you all know this :
>>
>> you write a script in MEL or PYTHON ... you go on working and working
>> - and you forget to save your script ... SUDDENLY maya crashes.
>>
>> e.g. the work for 4 hours ( IN SCRIPT EDITOR ) scripting is gone .
>>
>> QUESTION:
>> does maya somewhere store the "history" of the script-editor in one of
>> the windows-temporary-directories ?
>>
>> or might my "code" still be in my RAM somewhere , and i might find it
>> with a "HEX-editor" or any kind of MEMORY-search ???
>>
>> -----------------------------------------------------------------
>> does anyone ever found out , how to deal with this problem ?
>>     
> >
>
>   


--~--~---------~--~----~------------~-------~--~----~
Yours,
Maya-Python Club Team.
-~----------~----~----~----~------~----~------~--~---

Reply via email to