first In your plugin declaration with the kDoubleArray output I would
rather correct those lines( things can be done in a lot of different ways,
this is how i do it ):
"
def initializePlugin(mobject):
fnPlugin = omMPx.MFnPlugin(mobject)
fnPlugin.registerNode(nodeType, nodeId, nodeCreator, nodeInitializer)
"
by
"
kPluginNodeName = "spaceSwitch" #<-- replace by your plugin name
kPluginNodeId = OpenMaya.MTypeId(your_Custom_ID_number here)
def initializePlugin(mobject):
mplugin = OpenMayaMPx.MFnPlugin(mobject, "AuthorName", "VersionNum", "Any")
mplugin.registerNode( kPluginNodeName, kPluginNodeId, nodeCreator,
nodeInitializer, OpenMayaMPx.MPxNode.kDependNode)# <-- As you can see I use the
type of the node here a dependency node
"
then In your compute method there is no code to write some value on your
output and also no setClean call.
Your node must also be connected to another node. just few question bellow,
Are your example the complete code for your nodes?
Do you have an ascii maya file that can be used as an example?
Do you have any prior experience with the API?
Have you a basic understanding of the concept of hierarchy , connections ,
attributes and plug ?( DAG versus dependency nodes )
Le vendredi 8 juin 2012 19:51:19 UTC+2, WhileRomeBurns a écrit :
>
> Thanks for the quick replies! So he basically tricks Maya into dirtying
> his plug in the draw method? Nice. So in my example, I would query the
> value of a third dummy attribute- something lighter weight than an array
> like a float or int and use that to force the eval? Can do!
>
>
> * > how about writing a node to compute your pointList and plug it to
> your locator that will only draw from *
> Absolutely the way to go, but I thought I would save time and test the
> idea in one node. But then nothing worked :)
>
>
> Additionally, I'm now fighting python just to call compute with *
> MFnTypedAttributes*. Two examples, slightly modified versions of
> Farsheed's skeleton code. The first one has MFnNumericAttribute as the
> output attribute and it calls the compute method as expected. The second
> one is bunk though and I cannot figure out why. Hmm. Take a look:
>
> nodeNumeric.py:
> http://pastebin.ubuntu.com/1030758/
> Works a charm, compute gets called.
>
> nodeTyped.py
> http://pastebin.ubuntu.com/1030764/
> Compute never gets called. Silently fails? Only changed the attr type to
> TypedAttr and kDoubleArray. Nada. Zilch. Zippo!
>
> Did I miss something obvious? Thanks.
> -shawn
>
>
>
--
view archives: http://groups.google.com/group/python_inside_maya
change your subscription settings:
http://groups.google.com/group/python_inside_maya/subscribe
