RH8: Tree shortcuts are not working

The Grasshopper shortcuts for Flatten, Graft, etc. are currently not working in Grasshopper 1 for RH8 on Windows.

2 Likes

Hi @rudolf.neumerkel thanks for reporting, I’ve added RH-73289 shortcuts for graft, flatten no longer work in gh1

ps: your text says ‘now’ instead of ‘not’

1 Like

You mean “not working”, eh?

small difference yes :smiley:

@DavidRutten, after reading your response on YoĂźTrack:

This topic might be helpful, as those parameter shortcuts did not work on Mac as well. Curtis then came up with a fix:

Parameter input keyboard shortcuts missing - Grasshopper / GH for Mac - McNeel Forum

The problem is still very much present in the latest Rhino 8 Beta. It gives you headache not being able to use ‘WH’ or ‘G’ as shortcuts.

Any hope in the vicinity? @Gijs or @DavidRutten
I understood from the YouTrack that it “just worked” in the first place, but is there a way to actually build it as a feature now that something has clearly changed with Rhino 8?

3 Likes

It was working but is not working anymore on RH8 Mac as well…

I too am having pains with Rhino 8 Grasshopper due to these shortcuts not working. It’s really slowing my usual workflow. With each service release I hurry to check and see if they work again.

2 Likes

on Mac I can at least press F and then confirm with Enter. Confirming with Space is not possible anymore, which is easier to do with one hand.
Ideally F, G, etc. hotkeys will work again…

100% agree. Having to navigate the right-click menu means my mouse hand has to do so much more maneuvering and clicking than before, which is contributing to fatigue.

this issue (fixed) is now logged under
RH-82929 Grasshopper: Parameter input keyboard shortcuts required enter or space to complete

Note there is also RH-57216 Grasshopper: Parameter input keyboard shortcuts required enter or space to complete

On Mac it currently partly works.

529 days (1 year, 5 months and 13 days) after it was reported on this thread - and still only partly fixed on Macs. Amazing (not in a good way).

Things get fixed and sometimes break again, that’s what you can see if you read the history in that YT. Many of the bugs get fixed quickly, some take longer, either because they are more complicated to solve, or because there are other issues that are given higher priority.

Some never get fixed at all, like the ‘Variable x’ bug on expression components when switching to ‘Display | Draw Full Names’. In this case, 1.5 years and still only “partly works” on Macs should be embarrassing.

And rare, but it’s not. Many of “the bugs [that] get fixed quickly” should never have seen the light of day, to be reported by paying (and suffering) customers.