Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Feature: Reload local nodes #41

Closed
Banbury opened this issue Mar 24, 2023 · 1 comment
Closed

Feature: Reload local nodes #41

Banbury opened this issue Mar 24, 2023 · 1 comment

Comments

@Banbury
Copy link

Banbury commented Mar 24, 2023

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.

@KennedyRichard
Copy link
Collaborator

Mr. Banbury,

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.

Peace.

@IndiePython IndiePython locked and limited conversation to collaborators Mar 24, 2023
@KennedyRichard KennedyRichard converted this issue into discussion #42 Mar 24, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants