"Update all trees" is too dangerous action

[rendetto]

Referring to (https://github.com/nortikin/sverchok/issues/4236) I got a thought. What if you accidentally press the "Update all trees" button - it will freeze or even crash Blender, especially in my case with so many and heavy trees. It's too close to "Start Live Update" button - which I use a lot.

In terms of UI usability it's not a good solution to have such dangerous button next to frequently used one.

The new way does not imply preventing such mistake.

On the other hand - the old way of updating only the "P-enabled" trees is more user safe.

Can we make wider discussion on that topic? It's kind of important I guess.

Thanks

[rendetto]

Another user case I can think of (that's very common to my workflow) - unfinished trees, wrong trees, obsolete trees, trees that work only partially, tree segments, temporary trees, etc... All those are included in the list which is supposed to be updated by the new "Update all trees" button. How we can prevent those from being updated? Let's say I have 15 trees that need to be processed and 5 that are just rough ideas and not functional(or are even damaging) - do I have to press Re-update separately to all 15 that I need to process - seems not practical to me.

Do we need "Update all trees" button in the sense of the new update system? It could do more damage than being useful.

I think we need a way to mark only those we need to update, and have an "Update selected trees" button (similar to the behavior of the previous update system)

Please share your opinions. Thanks

[Durman]

What if you accidentally press the "Update all trees" button - it will freeze or even crash Blender, especially in my case with so many and heavy trees. It's too close to "Start Live Update" button - which I use a lot.

Actually this update should be cancelable. I'm not sure about correctness of the message in the header but seems Escape button should work. http://nortikin.github.io/sverchok/docs/tree_evaluation_system.html#progress-message

Okay, I don't think there will be any harm to have an extra button. The new button should do the same as Update all but do this only for trees which are active.

All what should be done is to copy existing operator, rename it and add extra check if tree.sv_process: tree.force_update() https://github.com/nortikin/sverchok/blob/550427bbfc63507fe5d6eaf35830cb9aa454d196/ui/sv_panels.py#L208

After that the operator should be added to the UI in the same way as it is done for Update all operator. https://github.com/nortikin/sverchok/blob/550427bbfc63507fe5d6eaf35830cb9aa454d196/ui/sv_panels.py#L47

[rendetto]

Actually this update should be cancelable. I'm not sure about correctness of the message in the header but seems Escape button should work.

It kind of works. It's not instantaneous and needs some time(sometimes several minutes) to halt the processing. I guess it depends on the current node that is being processed when the Esc was pressed.

Okay, I don't think there will be any harm to have an extra button. The new button should do the same as Update all but do this only for trees which are active.

@Durman Thank you. That will be great.