When working on Isolated objects (Select, ‘Isolate’, ‘Unisolate’ etc.) Rhino regularly forgets what’s happening, saying “No objects are hidden” when trying to ‘Unisolate’. This means I have to ‘Show’ all objects and lose tracks of anything that was hidden.
True, I’m always a little stressed when using Isolate.
I tried a few times but haven’t been able to reproduce it deliberately yet.
@barden00 Good to know it’s not just me.
I find that undoing the isolate and then redoing it will clear the isolate cache, but that’s the only time I’ve had this issue - so I try to not to redo past it without a fresh isolate command.
1 Like
i can confirm that, when you do undoes in the isolate mode it can cause unisolate not to work anymore. that hurts a lot when you have a very complex scene open. and have to show all and work 10 minutes to get it the way it was…
i believe also isolating stuff, saving then quitting and reopening the file caused the unisolate not to work anymore, this or in combination with using once undo during isolate
this is also quite an old bug, i have reported that miles ago in some lost and forgotten topic.
Hi @encephalon, @NeilE,
Isolate and Unisolate are just a glorified versions of these two command macros.
I believe you are correct. However, we’ve never been able to repeat.
– Dale
1 Like
did you ever have this happening? i assume this only happens on the mac version of Rhino?
i tried to repeat that and was lucky but the problem is to get it to happen one has to nearly erratically cmd z and cmd y to repeat in and out of isolate, i believe maybe it also involves cmd tabbing to a differen app and back while being in isolate having maybe just cmd y into isolate plus one or two steps. but i can not nail it down.
I have not. But I also am not a frequent user of this.
– Dale
I’ve used these words alot over the years, but never as actual commands, are you saying thiese are actual commands? 
oh I see:
that’s just another way of hiding/unhiding stuff 
yeah I guess I’ve seen those before.
Rhino has so many buttons
I just noticed this, are those real macros lol I was saying that the other day
exactly! lol 
Hi @dale
See this thread. I can’t believe you don’t know Isolate doesn’t work well and hasn’t since V5. From another thread which I can’t find one of the developers replied that it can’t and will never be fixed so as to circumvent it getting lost in the undo stack.
Here’s how to reproduce since you can’t remember.
Reviving this old thread to say this is still occurring. It’s easily reproduced in a new file:
- Create a few objects.
- Isolate one of them.
- Unisolate
- hit undo to undo step 3
- Try to unisolate again
- “No items hidden”
The pain here is that now you’ve accidentally added a bunch of items to your hidden items. You can’t separate the hidden items from the items that were only hidden because you isolated them in step 2. So, you have to go into your hidden items and unhide everything except the items that you really wanted hidden.
Command History:
Command: Isolate
2 extrusions added to selection.
Command: Unisolate
Showing 2 hidden objects.
Command: _Undo
Undoing Unisolate
Command: Unisolate
No objects are hidden.
Isolate needs work for the undo command
RM
3 Likes
I just use the ‘invert’ and ‘hide’ or ‘unhide’ etc. I’ll have to check out those ‘isolate’ ‘unisolate’ commands though. I wonder what their macros look like, or how they can be different.
Hmm, looks like they have their own secret programming:
Well, Isolate was added to Rhino 6:
– Dale
1 Like
I never have used the Isolate command because when I first tried it did work as it was advertised to do.
Its a pretty simple concept and its indeed sad that Rhino developers cannot grasp the basic concept of what it is supposed to do and how to implement it.
What I do if I want to isolate something is select everything else and group it then hide the group. I can then reverse the process without fail. Needless to say with that process you can go forward or reverse with undo or redo without problem. Isolate is just another one of the numerous half-baked commands that never were fully implemented.
I also tend not to hide a lot of things. I prefer to create one or more layers as dumping grounds for objects that may or may not be useful but need to be hidden.
1 Like
Hi @dale
So you don’t even know of the reported shortcomings of the command yet you are a programmer who asked how to reproduce this and when I showed you a way how to reproduce the issue you come back with a childish answer that it was not a command in V5. Does that mean you don’t care about fixing the issue even after you were shown how to reproduce the issue.
Here is another thread from V7 pre release that shows where the command currently stands when it was a command and you don’t know of these issues? Nor tell the people of this thread about it. You answer this thread and have no knowledge of this command or it’s shortcomings and yet you work at McNeel.
RM
Please fix Isolate command and make it respect undo redo - Serengeti (Rhino WIP) - McNeel Forum
Hi All,
This issue should be fixed in Rhino 8 SR6.
– Dale
3 Likes
Any chance the bug fix could make it to Rhino 7 please? It’s a regular annoyance and avoiding it is a workflow change that I adjusted to early in my Rhino days but not having to work around it anymore would be nice.
1 Like
Hi @vcruzdesigns,
It’s my understanding that we are not making changes to Rhino 7 anymore, unless some catastrophic issue is discovered.
– Dale
1 Like
amazing! thank you @Alexander_Kaplan for nailing it down and @3dsynergy to reference the report… finally this is getting fixed… or is it?
what does should mean?
1 Like
I’m not sure if you intended this to be snarky, but he’s suggesting we give it a try and see if there’s a sneaky bug missed in the development. Nothing’s perfect.
I’m surprised and appreciate the additional work being done to fix this nagging issue with isolate/unisolate.
2 Likes