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

Gallery Group Nodel delete member #21

Open
scienceworld opened this issue Oct 3, 2017 · 5 comments
Open

Gallery Group Nodel delete member #21

scienceworld opened this issue Oct 3, 2017 · 5 comments
Assignees

Comments

@scienceworld
Copy link
Contributor

Deleted a member from a gallery node with group support and received this error.

10-03 10:29:49.26 ('main' and '@after_main' functions completed cleanly) 10-03 10:30:00.59 PowerOn requested. 10-03 11:01:45.15 (closing this interpreter...) 10-03 11:01:45.15 (clean up complete) 10-03 11:01:45.21 (Python and Node script loaded in 56ms; calling 'main'...) 10-03 11:01:45.21 Started! 10-03 11:01:45.21 'main' completed with errors - Traceback (most recent call last): 10-03 11:01:45.21 File "C:\Nodel\.\nodes\BodyWorksGallery\.nodel\nodetoolkit.py", line 283, in processAfterMainFunctions 10-03 11:01:45.21 f() 10-03 11:01:45.21 File "C:\Nodel\.\nodes\BodyWorksGallery\script.py", line 282, in extendGroup 10-03 11:01:45.21 desirePower.addEmitHandler(handlePower) 10-03 11:01:45.21 AttributeError: 'NoneType' object has no attribute 'addEmitHandler' 10-03 11:01:45.21

@scienceworld
Copy link
Contributor Author

problem exists when legacy support is enabled, and there are no members. disabling legacy support corrected issue.

@rhulse
Copy link
Contributor

rhulse commented Oct 3, 2017

@scienceworld I have seen a similar issue when deleting members - in may case, the old data was not removed from the config json file, so the group node was still looping over it. Perhaps check the config in the editor for the node to see if the old data is still there.

@scienceworld
Copy link
Contributor Author

i'm sure that was the case. either way turning off legacy support got around the problem.

@scienceworld
Copy link
Contributor Author

got it to a position where deleting the members caused the entire recipe to error out and no longer function. I ended up re-adding the member to get it working again. haven't tried cleaning out the config.json but we ended up having a gallery that didnt power on or off for a few days as a result of not catching this.

@scienceworld
Copy link
Contributor Author

confirmed that a gallery node with groups bolted on with no members causes the recipe to no longer present any actions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants