There is a huge problem once the “Isolate” is already in use and the user wants to select a bunch of objects based on two criteria. That makes the “Isolate” tool not usable, because repeating it will hide the rest isolated objects and then the “Unisolate” command will show all objects instead of the previously isolated ones.
As a (risky) workaround I use a secondary “Isolate” script, but there is a catch: If I happen to unisolate with the default “Unisolate” command of Rhino, it loses track which objects to show and literally deletes forever the visibility state of the entire scene. This is why it’s extremely important to remember whether that script is active when unisolating. In this case that must be done with its own “Unisolate” command instead of the default “Unisolate”.
An other problem with using that script is that it will not remember which objects were temporarily hidden during the isolation after the file is saved, closed and then opened again.
Isolate Selection:
_-Invert _-Hide _Pause "TempIsolate" _Enter
Unisolate Selection:
! _-Show "TempIsolate"
Another alternative isolation:
IsolateX Rhino 6.rvb (5.4 KB)
Isolate.rvb (5.4 KB)
Isolate objects.txt (184 Bytes)
