You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the development of new nodes it would be convenient, if I could reload all local nodes at once.
All nodes in the current graph would need to be redrawn, and invalid connections deleted.
Auto reloading when a node is changed, would be even better.
The text was updated successfully, but these errors were encountered:
Thank you for your feature request. All improvement suggestions are welcome and represent a chance of steering the app towards a successful path.
I'll properly reply to your suggestion in a day or two, this message is just so you know I'm aware of it.
I'll also take the liberty of converting your issue into a discussion, but don't worry about it, it doesn't mean your request is any less important. It is just that in Nodezator and other Indie Python repos we use issues for things that crash the app or otherwise prevent the user from doing something that is supposed to be available. When such an issue appears, any other work is paused so that it can be fixed ASAP.
This measure is taken for the benefit of the users: by doing things this way, whenever you have a real issue, it won't compete for space with other less urgent matters, just like your issue #40 that was given priority over other development tasks because it was a real issue (something that crashes the app).
A feature request is as important as an issue, but doesn't have the same urgency.
During the development of new nodes it would be convenient, if I could reload all local nodes at once.
All nodes in the current graph would need to be redrawn, and invalid connections deleted.
Auto reloading when a node is changed, would be even better.
The text was updated successfully, but these errors were encountered: