It's correct that saveFile was mistakenly not in the version released in 2011; this has been fixed, and it is present in 2012.
However, there's still no need to go back to mel.eval - you can always just use cmds.file(save=1, force=1). I'll look at why pm.mel.file(save=True,force=True) isn't working... - Paul On Wed, Apr 27, 2011 at 9:10 AM, hapgilmore <[email protected]> wrote: > There is no file() function in pymel. All of the mel 'file' commands > have been replaced with commands like saveFile() openFile() > importFile() etc. > > Read the docs for pymel.core.language.Mel. I have to use it all the > time when a mel command is broken or not implemented in the core > namespace. I don't like to use it, as it handles errors differently > and returns strings instead of pynodes. > > Even worse is mel.eval() which I use as a last resort to bypass python/ > pymel completely because something is really broken...like in this > case. > > > On Apr 27, 9:24 am, Amorano <[email protected]> wrote: > > Isn't it just: > > > > pm.file(s=1, f=1) > > > > I dont think you use the mel namespace for cmds in the core namespace. > > > > On Apr 25, 3:33 pm, hapgilmore <[email protected]> wrote: > > > > > > > > > > > > > > > > > PyMel v1.0.0 docs document a saveFile() function, but it's not in Maya > > > 2011's pymel. Is this a known issue, or am I missing something? > > > > > Interestingly enough: > > > > > pm.mel.file(save=True,force=True) > > > > > doesn't work... > > > > > In the meantime: > > > > > pm.mel.eval('file -save -force') > > > > > will have to suffice? > > -- > http://groups.google.com/group/python_inside_maya > -- http://groups.google.com/group/python_inside_maya
