Hi…,
the latest Rhino WIP confuses me, I can’t subselect surfaces of a polysurface (CTRL+SHIFT+LMC or Drag Window). Here a test-file: box_colored.3dm (1.3 MB)
What I am missing?
Thanks
Michael
www.flexiCAD.com
I can sub-select the faces of your object here - but there is some really weird sh** going on.
In Rhino WIP running in English, if I Ctrl+Shift +Click on a face, I get the multi-selection box which asks me to choose either the face or… the whole box. Drawing a new basic box in the same file doesn’t do that, only the face selects. And this even if I copy/paste your object to V7.
In Rhino WIP running in German, if I hold down Ctrl+Shift and just mouse over a face, it lights up. But I still have to click to select the face. No multi-selection box comes up however. And the mouse-over lighting up (interesting phenomenon) doesn’t happen when running Rhino in English…
1 Like
Michael’s box is grouped as well as joined - that appears to be what causes this particular different behaviour.
1 Like
Ahhh… I looked to see if there were several objects that might be grouped, but I didn’t think to check if the object was in a group by itself…
There appears to be a bug in the WIP which isn’t displaying isocurves in the Wireframe view, even with Isocurves ticked in the options. So you have less opportunity to make selections.
Apart from this though, sub surface selection appears to work the same as in 7.
HTH
Jeremy
IIRC this is not a bug but a setting now for planar surfaces. I forgot where to turn it off.
1 Like
Ah, thanks Mitch. I found it in the Advanced Options as Rhino.Options.Display.ShowIsocurvesForFlatBrepFaces. I think I’d rather the default behaviour was for this to be On, mimicking previous versions of Rhino.
@Michael_Meyer, you might wish to turn this on.
Regards
Jeremy
The grouping thing still doesn’t explain the difference between the WIP in English and in German here… The following is after ungrouping in both versions (no mouse clicks in the second part, only mouseovers):
Looks like this is controlled in Advanced Options, so I’d compare your Germanic and English settings. The relevant options are:
Rhino.Options.General.MouseOverHighlight set to Off
Rhino.Options.General.MouseOverHighlightSubObjects set to On
This combo gives the Germanic behaviour.
Setting the first option to On make the whole object highlightable in the Germanic style and makes the second option irrelevant.
Setting both options to Off gives the English behaviour.
The Germanic behaviour appears to be the default.
HTH
Jeremy
1 Like
Yep, that’s it, my English version was modified, the German one not. I had no idea these settings even existed.
I guess we’ll keep stumbling on stuff like this as the WIP tacks toward harbour.
Default as Off has been explained as causing users to see that the option exists. Another setting for me to remember to change, similar to the default of control points being turned on when a curve is selected.
Only users who know the alternative will be “alerted” to the choice. That’s the existing customer base. I suspect more people in the customer base will want to keep isocurves than lose them, so having a default of Off means that more people have to waste time finding the setting and fixing it (or assuming as i did that the missing isocurves were a mistake) than will waste time if the option is On. New users won’t know what happened in earlier versions of Rhino and will therefore not be informed by the default, making the argument flawed for that customer segment.
All in all, a dodgy premise…
FYI, today after reopening this file, subselection seams to work as expected. Hm?