Ouch. Got it, really pity to hear that so good thing as scripted access to Maya internals left unfinished, but thanks for information.
The problem with api 1.0 is that i cannot find any documentation on it, seems it was intentionally replaced with 2.0 wherever it was possible, and some methods changed a lot, like MFnMesh.allIntersections parameters list. On Tuesday, May 19, 2015 at 7:19:16 PM UTC-4, elrond79 wrote: > > Hey Kthulhu - > > The python api 2.0 was a very promising start that was sadly left only > half-finished. So a lot of functionality (including many of the iterators) > is simply missing. It's a bummer, because api 2.0 was both way simpler to > use, AND way faster than the 1.0 python api. > > Because it's only half-finished, though, the only places I use it are very > self-contained tasks, that I know can be accomplished with it, and could > use a speed boost (compared to 1.0 python). > > - Paul > > PS - Please remember I tried to help, when your dark shadow covers the > world, and you're trying to decide whose soul to devour. Thanks... > > -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/fe67defe-9644-4d16-9611-185964ed0839%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
