Windows access keys which allow selecting options with one key from right click or other context menus are not working in Rhino 8 SR2 (822346.13001, 12-12). Options from the very top bar (e.g. File, Edit, View, etc…) do work as expected, but Grasshopper and any toolbar within a container do not seem to work.
Example: Previously in Rhino 6/7 you would be able to collapse all sublayers by right-clicking and then hitting “C” on the keyboard. After the right click on Rhino 8, the keyboard entry will start typing in the command line. These windows shortcuts can typically be viewed by holding down the alt key when opening a context menu.
This seems to be related to the issues seen with the flatten and graft shortcuts within Grasshopper mentioned here: RH8: Tree shortcuts are not working
For some reason, those “fixed” messages are sent out when the issue goes to “Needs Testing”. When the tester then decides the issue is not fixed, it is reopened.
When a public build is released between the point where the issue goes to “Needs Testing” and actually gets tested, the “fixed” message might be premature.
-wim
We want everyone to test fixes, not just our internal tester. So we don’t require our testing staff to agree that it’s done before we announce it. This gives us faster feedback from customers.
Windows 10 (10.0.17134 SR0.0) or greater (Physical RAM: 16GB)
.NET 7.0.0
Computer platform: LAPTOP - Plugged in [100% battery remaining]
Non-hybrid graphics configuration.
Primary display and OpenGL: NVIDIA Quadro P2000 with Max-Q Design (NVidia) Memory: 4GB, Driver date: 12-1-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 537.99
> Integrated accelerated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Primary OpenGL: NVIDIA Quadro P2000 with Max-Q Design (NVidia) Memory: 4GB, Driver date: 12-1-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 537.99
> Integrated accelerated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Secondary graphics devices.
Intel(R) UHD Graphics P630 (Intel) Memory: 1GB, Driver date: 2-18-2021 (M-D-Y).
> Integrated graphics device with 3 adapter port(s)
- There are no monitors attached to this device. Laptop lid is probably closed
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 12-1-2023
Driver Version: 31.0.15.3799
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 4 GB
Agree with you the whole RH8 UI is laggy and lost lots of efficiency in the workflow(in GH as well). How long could it take to have those issues fixed? Just got Rhino 8, but I can’t use it in its current state.
( Can it be linked to the Mac and Win UI coinciding? key acces in menus doens’t work on Mac os, if i remember well )
thanks
hi @q.andreotti General statements won’t give us any info on what works and what doesn’t for you. It will be helpfull if you you list the issues you are facing, so they can be logged and addressed, thanks!
That YT is for layer panel drag to select. In addition, my video gif demonstrates the OP’s bug, failing Windows shortcut keys, in my case E and C for expand and collapse, within the layer panels.
Windows access keys are probably the fastest way to work, generally. I consider it essential to have them available. Command line + access keys + mouse = enormous efficiency potential.
Rhino 8 has eliminated most, if not all, of them in favor of forcing the user to mouse click to select something throughout the UI. To say this blunder is terrible would be an understatement. It’s purely a removal of functionality, and keeping them available in every menu wouldn’t get in the way of the times a user would want to mouse click instead.
Thanks @anon,
With the transition of Rhino 8 from .NET Framework to .NET Core, coupled with efforts to unify the user interface between macOS and Windows, it stays curious to me that the keyboard shortcuts have disappeared in this version. Given that macOS does not traditionally support keystrokes in context menus and pop-ups, this correlation seems more than coincidental.
While I recognize the immense benefits and the challenges involved in creating a consistent cross-platform experience, these shortcuts were crucial to many of our workflows.
Has anyone else noticed this, or are there explanations or workarounds that might have been overlooked?
I am hopeful for a resolution or at least an explanation to better understand the direction Rhino 8 is taking with these changes.
I suspect you’re right, and this suspicion fills me with dread.
(If I wanted a mac, or a touchscreen, I’d buy one.)
I say they still “are” crucial, and I hope Rhino 8 gets itself back on track and restores this essential functionality. Rhino 7 already started to lose its way in that regard with certain right click menus. At this point I can only have hope.
What is it going to take for access keys to come back throughout the UI?
