Hey, whatever works. =) The nextUniqueName fix was just committed to the codebase, so it'll be in 0.9.2.
- Paul On Tue, Jul 28, 2009 at 10:42 AM, [email protected]<[email protected]> wrote: > > Thanks for the quick reply Chad! > > I'm not using the docs from pymel and instead using > http://pymel.googlecode.com/svn/docs/index.html > > I've been using these asuming they are always the latest :(, I'll take > a look at the latest docs! doh! > > Cheers for this, you would'nt believe the hacky way I'm getting the > next unique name. > > temp = pm.spaceLocator("theExistingName") > newName = temp.name() > pm.delete(newName) > CGFXNode.rename(newName) > > Horrible! > > Cheers > > -Dave > > > On Jul 28, 4:51 pm, Chad Dombrova <[email protected]> wrote: >> hey thirstydevil, >> >> > So far it's a huge >> > improvement, except for the docs, but I know they are changing, Guess >> > I'm used to the mel docs. >> >> can you elaborate on what you don't like about the docs so we can work >> to improve them? are you using the docs that came with 0.9.1 or the >> docs from 0.9.0? we changed doc format between these releases, but >> the old-style docs are still here: >> http://pymel.googlecode.com/svn/docs/index.html >> >> >> >> > Keep up the good work. >> >> > However, I would expect this to work? Wondering why it's not? >> >> > CGFXNode = pm.PyNode("MSC_Lamps_cgfx") >> > if CGFXNode.name() == "MSC_Lamps_cgfx": >> > CGFXNode.rename(CGFXNode.nextUniqueName()) >> >> it seems nextUniqueName only works if the name ends with a number: >> >> p = PyNode('pSphere1') >> p.nextUniqueName() >> # Result: pSphere2 # >> >> i see what you're trying to do and i think it should work, too. i'll >> get this fixed up for 0.9.2 >> >> -chad >> >> >> >> > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/python_inside_maya -~----------~----~----~----~------~----~------~--~---
