RESOLVED: Containers can be “bypassed” but not easily un-bypassed

Bugs
1

I take it that containers are not supposed to be capable of being bypassed because they don’t have a bypass button on them, but you can “pseudo-bypass” one by this method:

Make a container and put an operator of any kind next to it, Drag select both of them and click the bypass button on the operator, now they are both bypassed even though you can’t bypass the container.

He tricky thing is, the only way to un-bypass it is to drag select the container and an operator again, again and - un-bypass the operator to toggle the bypassed flag on the container.

Not a huge deal, but a head scratcher for me today, as the container can’t call up its children to view in its preview window in this state.

For me personally It would be nice if drag selecting a container along with an operator and bypassing the operator bypassed all the containers child operators including any in child containers operators.

2

You can use Shift+t in the network to access list mode and then it’s easy to set the bypass flags.

Yeah, its a big of a bug that they can be bypassed in the first place.

3

Ah, thank you much. List mode will be very handy for lots of things, especially nuking unwanted operator displays… It appears to be a list created on the fly of the nodes that exist in my current area of my network? Do you where might I find some docs on it?

4

It is all the operators in the network you are in, a glance at everything. There’s nothing else to it right now, no help docs just the list.