With the solution that I posted above it’s possible to have up to 3 levels of isolation of objects. They all are an isolate command but work in a different way.
By the way, years ago @pascal created a wonderful script for Rhino 5 called “Isolate objects” with the following aliases: “_-Isolate” and “! _UnIsolate”. It had two cool features that made it special:
It asked whether to save and restore the current view upon isolation of the selected object(s).
It remembered the state of the isolated and temporarily hidden objects, so that even if you save the file and close it or if Rhino crashes, the eventual re-opening of Rhino and the file will let you unisolate the object(s) and bring back the temporarily hidden objects in the scene, whereas the truly hidden objects stay hidden.
Unfortunately, the native “Isolate” command in Rhino 6 has the same alias as this particular script, so it seems like it’s not possible to use the latter in Rhino 6 in order to take advantage of the two “remember and restore” features.
It’ may be very valuable for Rhino 5 users, though:
Combined with “Isolate/ Unisolate Selection” it allowed two levels of isolation in Rhino 5:
It was very handy to use primarily @pascal’s script as the main isolation way that let you save between sessions with isolated objects without worrying that the next time you open the file the temporarily hidden objects will not be remembered. And then, the “Isolate/ Unisolate Selection” script was useful for quick isolation of one or more objects that you needed isolated for a shorter time.