Click correct layer when changing from GH to RH windows

Rhino Rhino for Mac
, ,
1

Current Behavior:

  • With a RH model with multiple layers…
  • When changing from a GH window back to the RH window…
  • Clicking on any Layer’s state change button will always affect the ‘active’ layer, not the actual layer being clicked.

Example:

Desired Behavior:

  • Even when changing from GH to RH windows, a ‘click’ on a layer should affect the layer I am actually pointing at, not the ‘active’ layer.

Its not a huge thing, but it definitely ‘bites’ me quite often, causing unexpected layer state-changes (which can sometimes have annoying side effects if they accidentally trigger a GH re-calc).

Environment:

all the best,
@ed.p.may

2

Hi Ed -

I agree with the biting… In my experience with macOS, however, this is not a Rhino or Grasshopper issue. You can reproduce the same behavior when going from any other application to Rhino. Or between any two other applications on macOS. I always need to click twice as many times in macOS than I do on Windows. First click is to let the OS know that you have changed to a different application. After that, you can go on with business…
-wim

3

Hi @wim , glad I’m not the only one.

I think what I’m describing is a little different than what you are saying though. Going from GH>RH only takes one click for me, but it applies the click to the ‘wrong’ layer (always to the active one, not the pointed-at-one).

In Rhino for example, a single click does work as expected (the thing you point at gets clicked) when changing between GH>RH for all the other buttons and tool pallets (pallet? container? panel? window? the thing with the buttons in it :wink: ) in Rhino - just not the Layer tree. A single click even works for the buttons at the top of the Layer panel itself, it seems that for me this behavior is more limited to the elements inside the Layer tree:

in those other cases, for me at least, a single click is all it takes to both change context from GH to RH AND active the right button within RH. Thats the behavior I think would be the best with regards to the Layer tree elements as well.

@ed.p.may