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

Better default or option to set generated add-on operator location #80

Open
BrendanParmer opened this issue Jan 21, 2024 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@BrendanParmer
Copy link
Owner

No description provided.

@BrendanParmer BrendanParmer added the enhancement New feature or request label Jan 21, 2024
@BrendanParmer BrendanParmer added this to the v3.1 milestone Feb 9, 2024
@BrendanParmer BrendanParmer removed this from the v3.1 milestone Mar 17, 2024
@BrendanParmer
Copy link
Owner Author

This one needs more thought on what the add-on should actually do for a given node group. Its current location made sense when it was just applying a geometry nodes modifier to an object, but Blender and NodeToPython have grown beyond that. A distinction should be made between full node groups, which you might use as a full modifier, tool, material, or scene compositing node tree, and helper node groups, which may only be used as building blocks.

These helper node groups should go under NODE_MT_add, since that's where other node groups go. The full ones seem less obvious to me. Should NodeToPython even be responsible for automatically applying geo node modifiers, assigning materials, creating new scenes, etc? I'm curious how (or if) people are using the add-on mode and what improvements everyone would like made to it

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

No branches or pull requests

1 participant