Seriously? V8 Deselect still broken -> Edit: sorry my bad

create two curves, select both, press CMD + left mouse button to deselect one of them → nothing happens.

i thought i am getting crazy with this not working and never actually realising and mostly just too busy to actually become aware of it, so i finally opened v7 to compare and see if i have been drugged all the time believing that this once worked, yes and there it thankfully works.

i cant understand why people have to torture themselves with a broken Rhino with such basic functions for that long, that is seriously unbelievable and just points out once more that nobody from the developers never ever touches Rhino for Mac for some actual work and not just for development. (at least i assume this is only on Mac since if that would be on Windows somebody would have probably come forward much earlier)

can we please have these basic functions finally fixed? i really dont know what to do anymore, how often have been people calling you out on how messed up v8 is? what is going on? are you doing it purposely??

works here in 8.12, what is your systeminfo?

For sure this works on Windows, but I am also really surprised if this has been broken from the beginning, that someone (besides yourself) among the 25% MacRhino users has not reported this earlier… Have to drag my Macbook out and test.

Working here on Rhino 8.10.24198.10002 on mac and my latest dev build on mac

the confusion keeps growing, at least i figured out how to reliably reproduce it.

create 2 curves, select one then use shift to select the 2nd, now try again with cmd click on one of them any luck?

when i simply window select both and use cmd click it works, not so if i use shift to select further objects before. thats why it took me some time to figure out that something is actually wrong because i dont use shift to select further objects all the time.

Untitled.txt (12.8 KB)

Really appreciate this, it helps us a lot :slight_smile:

This still works correctly for me. I’ve tested the same version of Rhino on an M1 and an M3, but I am on a later Mac OS so it could be that. Can you try it with 3rd party plugins disabled?

i believe i had only bella and vectorize, but that did not help.

also cmd window select does not work, once i select a 2nd object with shift deselection is bricked.

maybe, but i also can not update currently. any way to check it on ventura? it is not that old and exotic i hope :crossed_fingers:

edit: i have some more input, it seems to have to do with points showing automatically, those that display points do not deselect, that means if you have 2 objects and you only select one more then the last one shows points and this one can not be deselected those with no points showing do actually deselect, but if you shift select 2 more objects instead of only one then the points do not show so the deselection process works again everywhere

so, anybody to take on that issue? @CallumSykes i edited my post since i found some more pointers to how its happening.

OK, I pulled out my MacBook Pro (M1) and installed the latest 8.11 SRC.

  • Set control points to turning on when selecting curve objects (options>mouse)
  • Made 3 polylines
  • Selected one, it highlights and points turn on
  • Shift-clicked on a second one - it highlights and points also turn on
  • Cmd-clicked on the first one - it deselected and points turned off.
  • Shift clicked on the first and third - now all three are on with points on
  • Cmd clicked on each in turn, they all deselect and points turn off…
  • Cmd window or crossing works to deselect as well

What am I missing in your procedure?

@Japhy, @CallumSykes my sincere apologies, i fiddled with the settings which clearly is for more advanced users i was just curious and unchecked it and forgot all about it. now i know what its for.

:flushed: :melting_face:

try with Rhino.Options.General.PointsOnObjectSelect set to false in case you are in need of the same experience :smile: oh and thanks for trying to replicate, sorry about that.

4 Likes

No worries @encephalon, I can see that would have been annoying. Is there still a bug here with that advanced setting? Or is everything working as you expect?

Thanks. I’ve put this on the list as RH-83514 Settings: Advanced Setting Causes Deselect to Fail
-wim

thanks @wim i thought i felt dumb enough till you discovered its a bug after all, now i am really confused, what is this option actually for? if its a bug as you say and i saw it has been fixed, what can i expect to be different?