Rhino BETA Feature: UndoSelection /RedoSelection

Will there be an option to automatically pan the camera to the previous selection, so that it will be set to the center of the viewport? Not rotate, only pan.

Another useful approach would be to also remember the viewport state when the (sub)objects were selected, so that the user will be able to get the exact same view perspective like before. Solidworks saves the viewport state with the undo command, so, for example, if you go back to a certain older step of the modeling process, it will restore the view to the corresponding geometry.

Can you add something like OOPS command from autocad too. It brings back last deleted item.

SelectionUndo
SelectionRedo
SelectionStackPurge ?

i like a lot to have
SelCrv
SelclosedPolysrf
Sel…

@davidcockey i totally agree on having names starting with selection.

My strongest wish for Named Selection would be to add “boolean” / logic operations … my post in another topic did not get much attention:

Ok, I just tried this and it seems that the Undo/Redo Selection works in batches? Like if I select multiple objects one after another or multiple edges/faces and hit undo, it deselects all the (sub)objects and goes to a previously selected object from a different “selection batch”. I can see how this can be useful in cases like in the video in the first post.

But tbh, I was excited to use this when I miss-click and accidentally select a different object, or worse, sub-object where deselecting the correct thing can be a pain (same with lots of overlapping objects in wireframe/ghosted view where I often keep deselecting the wrong objects). And in this case, the new feature doesn’t help at all.

Probably not the best demonstration but I hope it gets the point across:

What it does help with is if I accidentally deselect everything (typically missing a gumball handle and inevitably losing the selection), so there’s that at least.

On the other hand, I can see where if used for these temporary multi-selections, it would be annoying to go through all the selection steps one-by-one. So I don’t know, feels like the only catch-all solution would be to have two different commands, one that undoes each and every selection ever made and one that undoes the whole batch. Too complex? Opinions?