Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RBF manager failing to update the UI #124

Closed
liorbenhorin opened this issue May 18, 2022 · 0 comments · Fixed by #125
Closed

RBF manager failing to update the UI #124

liorbenhorin opened this issue May 18, 2022 · 0 comments · Fixed by #125
Projects

Comments

@liorbenhorin
Copy link
Contributor

when selecting an existing setup, the UI is not propagating, and this is the traceback

# Warning: Python callback failed # 
# Error: (kInvalidParameter): No element at given index
# Traceback (most recent call last):
#   File "/Applications/Autodesk/maya2022/Maya.app/Contents/Frameworks/Python.framework/Versions/Current/lib/python3.7/site-packages/pymel/core/__init__.py", line 213, in _pluginLoaded
#     api.MEventMessage.removeCallback(_pluginData[pluginName]['callbackId'])
# RuntimeError: (kInvalidParameter): No element at given index # 
Recording poses in world space set to: True
Default poses are zeroed: True
# Traceback (most recent call last):
#   File "/Users/liorbenhorin/dev/mgear4/release/scripts/mgear/rigbits/rbf_manager_ui.py", line 1202, in displayRBFSetupInfo
#     self.recreateDrivenTabs(self.allSetupsInfo[rbfSelection])
#   File "/Users/liorbenhorin/dev/mgear4/release/scripts/mgear/rigbits/rbf_manager_ui.py", line 1163, in recreateDrivenTabs
#     rbfNodes = sorted(rbfNodes)
# TypeError: '<' not supported between instances of 'RBFNode' and 'RBFNode'

image

@miquelcampos miquelcampos added this to To Do in mGear 4.x via automation May 18, 2022
mGear 4.x automation moved this from To Do to 4.1.x May 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 4.1.x
Development

Successfully merging a pull request may close this issue.

1 participant