It would seem that the connection between the option variable,
'workingUnitTime', and the actual time unit used, set by
currentUnit(t='pal'), is rather loose. There exists a mel function,
mel.syncPreferencesOptVars('syncCurrentToOpt'), which will update the
unit settings to match the option var (or vice-versa with
mel.syncPreferencesOptVars('syncOptToCurrent') ), but it doesn't do
everything that changing it from the preferences GUI will (such as
updating the time slider ranges). The stuff that the gui does can be
found in the prefsSyncSettings mel proc, in
$MAYA_LOCATION/scripts/startup/createPrefWndUI.mel. (You can find
that out, by the way, by switching on the History>>Echo All Commands
option from the script editor window, than changing the setting from
the gui.)
Also - note that currentTime has an 'updateAnimation' flag, which
will change keys so that they stay at the same time (but a different
frame number)... I think it's on by default.
- Paul
On Wed, Apr 28, 2010 at 9:11 AM, Ozgur Yılmaz <[email protected]> wrote:
> Hi everybody,
>
> a quick question, how can I set the working time unit (fps) by using pymel?
> If you answer is "use pymel.optionVar['workingUnitTime'] = 'pal' " it is
> just changing the optionVar, but not effecting the settings, as far as I
> see... there should be some command that updates the environment according
> to the optionVar settings...
>
> I also used optionVars while updating the playblast file name, it also was
> not recognized until I open up the playblast options.
>
> so any ideas?
>
> E.Ozgur Yilmaz
> Lead Technical Director
> www.ozgurfx.com
>
> --
> http://groups.google.com/group/python_inside_maya
--
http://groups.google.com/group/python_inside_maya
