Rhino7 bug: ERROR SELECT ALL WITH SELECTION FILTER

Rhino
#1

Title was going to be: Rhino7 bug: ERROR SELECT_ALL WITH SELECTION FILTER ONLY ALLOWING MESHES

INPUTS:
MESHES;
SURFACES+POLYSURFACES;
CURVES;
BUG:
if use Ctrl+A = SelAll and SelectionFilter only allows Meshes,
if there are meshes on the drawing area it will select only those…
but if not any meshes on the drawing area, it will select all entities (at least surfaces, polysurfaces and curves…)

I put the file in rhino that i was working just exported the screen objects working on, a screenshot so you can see my working/licence version, and a videeo in the following link

I think the video is well explanatory;
Thanks guys! :slight_smile: enjoying much more Rhino7 meshes operation. Great increment! well done!

#2

I see that here too…

1 Like
#3

Thanks you both.
I’ve put this on the list as RH-61841: SelectionFilter: SelAll overrides the filter
-wim

1 Like
#4

but not when the first selection happen… please state that… maybe missing an if statement :slight_smile:

#5

Hi -

I’m afraid I don’t know what you mean by this.
-wim

1 Like
#6

The first time you can see in the video, happens to be on the scene meshes and curves or surfaces… You have selection filter just selecting meshes… when you make SelAll just the meshes are selected… use that selection and make Hide… so now you just have objects that are not meshes… and that is when the selection filter is not respected when using SelAll again…

#7

Hi - videos tend to be difficult to follow and I had enough to test with based on your description.
There is no need for any first selection. Any time when the specified geometry type does not exist in the scene, the SelAll command overrides the filter.

Apart from that, the case where the specified geometry is present in the scene was described in my report.
-wim

1 Like
#8

Hi - this behavior turns out to be by design.
At some point, I thought that commands had to be special-cased to override selection filters when a command asked for specific input but the filter wouldn’t allow that.
It turns out that filters are generally overridden when they get in the way of executing any command.
In order to not have to set and reset filters all the time, when you run a command and the active filter(s) cause nothing to be able to be selected, the filters are disregarded.
-wim

#9

I think that is a wrong behaviour doesn’t make sense… it just comes out of the scenario where the filters where created for… You still have a “DISABLE” check box to disable it so you don’t have the software to do it for you in the case you specified… :frowning: