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
That's why the button is called "quit". We added it there since we had the errors that would cause NodeBox to go in an infinite loop of errors, and the only way out was to press that button.
...but perhaps it is a bit too drastic. It might be better if we take out the button entirely.
I don't think there is anything wrong with having the button there but
perhaps it should either only kill the instance/window that throws the
error OR relabel the button to something like "kill this and all parent
processes"?
Another option could be that if a new instance of nodebox is created then
it runs independently from any other instances?
On 13 Jan 2014 08:52, "Frederik De Bleser" notifications@github.com wrote:
That's why the button is called "quit". We added it there since we had the
errors that would cause NodeBox to go in an infinite loop of errors, and
the only way out was to press that button.
...but perhaps it is a bit too drastic. It might be better if we take out
the button entirely.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/363#issuecomment-32152613
.
The text was updated successfully, but these errors were encountered: