Home → NodeBox 3 →

Quit a Process || Undo a Node Connection || Ignore a Node (ON/OFF)

• Edit

thoolb

03 Dec, 2013 09:07 PM

Sometimes I can see the red dot in the upper right corner. It appears to tell: NodeBox is thinking. But most of the waiting time there is no red dot AND any user interaction is forced to wait. (It appears to tell: java is calculating?) - After such waiting time it happens occasionally that some previous user actions (while on hold) get run afterwards and quite fast.

For instance: you create a node connection which is quite demanding. While waiting you try to undo the connection by unconnecting the cable to interrupt the background process. You still need to wait. You try again to unconnect or try to select another node as rendered node ... Suddenly, as soon the first initiated task is done, all the following tasks go running.

• Interrupt: Is there any chance to quit a running process for situations especially those without red dot?

• Ignore: Would it be possible to set a node to 'OFF' to force NodeBox to both interrupt this nodes running process AND to IGNORE this node UNTIL it is set to 'ON' again? (sort of bridge mode for a node) (f.i. a tiny on/off symbol in a nodes corner or on a connection cable)

1. Support Staff 1 Posted by Frederik De Ble... on 04 Dec, 2013 10:56 AM

   

   Hi,

   The renderer runs in a separate thread and you should be able to interrupt it. However, the drawing happens in the same thread, which is why you sometimes have to wait while NodeBox has finished drawing. Someday the drawing might be done in a separate thread as well, which would make the application more responsive.

   We were thinking of adding a "manual" mode where NodeBox only evaluates the script when you specifically ask it to. This would solve the issue for big networks.

   Does this sound like it could solve your use case?

   F

   • Edit

2. 2 Posted by thoolb on 04 Dec, 2013 08:23 PM

   

   (...) you should be able to interrupt it.

   How would I start the interruption? A "command-dot" does not do anything. (mac os x).

   We were thinking of adding a "manual" mode where NodeBox only evaluates the script when you specifically ask it to. (...) Does this sound like it could solve your use case?

   No. My issue/lack as designer but non-programmer is that I try something (f.i. connect two nodes) without knowing about the result or how compute demanding it would be or not.

   So my idea is to immediately quit all processes which were initiated by NodeBox but without quitting NodeBox.app or its open files.

   p.s.:

   This would solve the issue for big networks.

   How do you mean/use the term "network" in this case? As a sum of all tasks initiated by a user/program?

   • Edit