I have used PyNode.__apimdagpath__() with much success! Are there docs, or even a list for all of these api object names? I can't remember where I found .__apimdagpath__, but I recall I just stumbled upon it somewhere.
-Ian On Dec 15, 9:59 am, Chad Dombrova <[email protected]> wrote: > keep in mind when you have to go to maya.OpenMaya you can use the various > low-level methods for getting access to the api objects > > PyNode.__apimfn__, PyNode.__apiobject__, PyNode.__apimobject__, > PyNode.__apimplug__, etc > > just be aware that we're considering changing the names to avoid the reserved > __*__ namespace. > > -chad > > On Dec 15, 2009, at 8:52 AM, hapgilmore wrote: > > > I used python in maya w/o pymel for 6 months or so. Pymel was a > > revelation when I discovered it. > > The best part is that a PyNode gives easy access to all the associated > > maya node's attributes, AND all the API functions related to the node > > type. > > > For example, getting API info from a polymesh is as easy as > > myMeshPyNode.numVertices() or myMeshPyNode.vtx[0].connectedEdges() > > > To get that in python without pymel, or MEL even, would require > > several lines of code. Occasionally I bump into an API function that > > doesn't work right in pymel and I have to do it old-school with > > Maya.OpenMaya.MFn commands, but those are few and far between. > > > Pymel and remote debugging in WingIDE have made my job 100X easier. > > > On Dec 13, 7:44 pm, Pyrokinesis <[email protected]> wrote: > >> Hello, > >> I would like to gain more insight into why you would want to use Pymel > >> in production? > >> Would anyone mind sharing their experiances? > >> Thanks. > > > -- > >http://groups.google.com/group/python_inside_maya > > -- http://groups.google.com/group/python_inside_maya
