Bug - unexpected rectangular selection in Wireframe

EDIT:
comparing filletSrfToRail in the latest WIP-Update Mac and PC-Side
I used vmware to check the Windows side…
Isocurves are not displayed - so i got a strange behavoir regarding selection.
hoping this issue get solved
I know that VMWare is officially not supported - see system requirements.

ORIGINAL POST:

Work In Progress
(8.0.23157.16305, 2023-06-06)

draging the white rectangle from top right to lower left
I get the shown unexpected selection.

I really hope this is a bug and not intended !
This is horribly unintuitive for wireframe, as I do not select any wires…

kind regards -tom

cornertest_tp_00.3dm (3.1 MB)

Hi Tom -

I have no idea what I’m looking at in that picture…
-wim

sorry i forgot to upload the file - see initial post now

@wim

sorry - forget about this topic - delete it if you want.

the problem is - vmware is not displaying the isocurves, but of course they are influencing the selection

Hi Tom -

I’m not going to test a vmware issue, but this behavior is also seen when you modify the default Wireframe display mode by turning off isocurves for flat faces, an option that was added in Rhino 8.
When you turn off isocurves for all surfaces, this behavior does not happen, and thus shouldn’t happen when using that new setting.
RH-75787 Selection: Surface gets selected when hidden isocurve is hit
-wim

still not fixed in current

or is there another bug - isocurves not showing at all for planar faces ?

Version 8 BETA (8.0.23290.13304, 2023-10-17)
Expires December 1, 2023

quite annoying bug

Hi Tom -

RH-75787 was fixed more than 2 months ago. If you find that it’s not fixed, I’ll need more information.

This different issue that you reported in a different thread is on the list as RH-77820 Display Metal: Isocurves on planar surfaces
-wim

dear wim - thanks for having a look at this.

should do the fix.

looks like isocurves are just not shown.
but the invisible / un-displayed isocurves still influence the selection.

so the displaymode setting does its job regarding selection.
but not regarding displaying.
the result / behaviour is the same as reported in this topic:
you select something that is not visible: