From 847ae2077105127a315e6c52e7ba555e90410d17 Mon Sep 17 00:00:00 2001 From: pfleer Date: Tue, 22 Aug 2017 14:20:18 +1000 Subject: [PATCH] add keyword args to pass through to addChildMetaNode --- core/Red9_Meta.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/core/Red9_Meta.py b/core/Red9_Meta.py index b6affae..f4dd6a7 100644 --- a/core/Red9_Meta.py +++ b/core/Red9_Meta.py @@ -3491,7 +3491,7 @@ def addSupportNode(self, node, attr, boundData=None): log.debug('Adding boundData to node : %s:%s' %(key,value)) MetaClass(node).addAttr(key, value=value) - def addMetaSubSystem(self, systemType, side, attr=None, nodeName=None, mClass='MetaRigSubSystem', buildflags={}): + def addMetaSubSystem(self, systemType, side, attr=None, nodeName=None, mClass='MetaRigSubSystem', buildflags={}, **kws): ''' Basic design of a MetaRig is that you have sub-systems hanging off an mRig node, managing all controllers and data for a particular system, such as an @@ -3510,7 +3510,7 @@ def addMetaSubSystem(self, systemType, side, attr=None, nodeName=None, mClass='M attr='%s_%s_System' % (side[0],systemType) if not nodeName: nodeName=attr - subSystem=self.addChildMetaNode(mClass, attr=attr, nodeName=nodeName) + subSystem=self.addChildMetaNode(mClass, attr=attr, nodeName=nodeName, **kws) #set the attrs on the newly created subSystem MetaNode subSystem.systemType=systemType