Just running a quick tutorial on grasshopper and I have fallen at the first hurdle. I have created a point parameter in grasshopper, but when I right click to set on point and reference rhino nothing happens, but parameter turns green - no drop down appears. Any pointers?
Running Rhino for mac 5.5.3
Hi - that seems to work fine on my system running 5.5.3.
Could you please run the Rhino About command, click on the More info… and then the Copy to clipboard button and paste the content back into a reply here?
-wim
Software information
Software versions
Rhinoceros version: 5.5.3 (5F88)
Rhinoceros path: /Applications/Rhinoceros.app
IronPython version: 5.1.2015.131
Language: en-GB (MacOS default)
macOS version: Version 10.13.6 (Build 17G6030)
Plug-ins
None
Third party kernel extensions
com.kairos.driver.DuetDisplay (1) 0A9F5387-316E-3D61-B9ED-D066346F8797
com.Cycling74.driver.Soundflower (2) 2D779840-7439-31E5-8A66-D786C3F47B75
Hardware information
Computer hardware
Hardware model: MacBookPro9,2
Processor: Intel Core i7-3520M CPU @ 2.90GHz
Memory: 16 GB
Architecture: Intel 64 bit
Video hardware
Graphics: Intel HD Graphics 4000 1536 MB
Memory: 1536 MB
Screen size: 1920 x 1080, 1280 x 800
Displays: PL2481H (94dpi 1x), Color LCD (114dpi 1x)
USB devices
Apple Inc.: iPhone
CHERRY: CHERRY KEYBOARD
Apple Inc.: FaceTime HD Camera (Built-in)
Apple Inc.: Apple Internal Keyboard / Trackpad
Apple Computer, Inc.: IR Receiver
Apple Inc.: Bluetooth USB Host Controller
Western Digital: My Passport 0820
Bluetooth devices
Apple: Apple Wireless Mouse
OpenGL information
OpenGL software
OpenGL version: 2.1 INTEL-10.36.23
Render version: 2.1
Shading language: 1.20
Maximum texture size: 16384 x 16384
Z-buffer depth: 24 bits
Maximum viewport size: 16384 x 16384
Implementation settings
Use texture compression: No
Appearance settings
Antialiasing: 2x
Mip map filtering: None
Anisotropic filtering: None
Thanks for that, Peter. Can you by any chance test to see if this works as it should in the Rhino 6 for Mac Beta?
@dan - any ideas on this one?
-wim
The only thing I can see here that is preventing us from reproducing this is that it is likely a High Sierra-only issue.
I’ll see if I can boot up High Sierra and reproduce this, but I doubt we will patch it because [reasons]. Given that we are not able to reproduce it on Mojave, I suspect it is a High Sierra-only bug…but that is pure speculation. If it were, I would expect we’d be hearing about it more, so it may be a combination of things.
Are you able to see if you get the same behavior in the latest RhinoBETA for V6?
I am unable to reproduce this in Rhino 5 for Mac 5.5.3 on High Sierra 10.13.6.
@peter15 I notice you have a couple of third-party kernel extensions…
I wonder if Duet Display is getting in the way here. Can you please boot macOS to safe mode and see if the bug is still present when these extensions are disabled?
Hi Dan, Wim.
I have changed to a standard mouse instead of the blue tooth apple mouse and this now works. Thank you for all of your help.
I’m glad it’s working. That is odd though as I use an Apple MagicMouse (Bluetooth). It’s not a great mouse for Rhino though (I switch to a three-button mouse with a proper scroll wheel when modeling).
On a Macbook pro here and Ctrl Click isn’t working as a Right Click, only in Grasshopper. Works fine with my mouse but sometimes I only have the trackpad…
Rhino 6 SR28 2020-7-17 (Public Build, 6.28.20199.17132, Git hash:master @ b1f15b655bd1f5ae0d3d3257e3efdeb0a45630e4)
License type: Commercial, build 2020-07-17
Apple Intel 64-bit macOS Version 10.15.6 (Build 19G73) (Physical RAM: 16Gb)
Mac Model Identifier: MacBookPro11,2
Intel Iris Pro OpenGL Engine (OpenGL ver:4.1 INTEL-14.7.8)
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: Height
Vendor Name: Intel Inc.
Render version: 4.1
Shading Language: 4.10
Maximum Texture size: 16384 x 16384
Z-Buffer depth: n/a
Maximum Viewport size: 16384 x 16384
Total Video Memory: 1536 MB
Graphics: Intel Iris Pro
Displays: Color LCD (221dpi 2x)
Graphics processors
Intel Iris Pro (1536 MB)
Color LCD (1440 x 900)
USB devices
Apple: Internal Memory Card Reader
Apple Inc.: Apple Internal Keyboard / Trackpad
Apple Inc.: Bluetooth USB Host Controller
Bluetooth devices
None
Rhino plugins
/Applications/Rhinoceros 2.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCycles.rhp “RhinoCycles” 6.28.20199.17132
/Applications/Rhinoceros 2.app/Contents/PlugIns/NamedSnapshots.rhp “Snapshots” 6.28.20199.1002
/Applications/Rhinoceros 2.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/GrasshopperPlugin.rhp “Grasshopper” 6.28.20199.17132
/Applications/Rhinoceros 2.app/Contents/PlugIns/PanelingTools.rhp “PanelingTools” 6.28.20199.1002
/Applications/Rhinoceros 2.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Commands.rhp “Commands” 6.28.20199.17132
/Applications/Rhinoceros 2.app/Contents/Frameworks/RhMaterialEditor.framework “Renderer Development Kit” 6.28.20199.1002
/Applications/Rhinoceros 2.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RDK_EtoUI.rhp “RDK_EtoUI” 6.28.20199.17132
/Applications/Rhinoceros 2.app/Contents/PlugIns/Displacement.rhp “Displacement” 6.28.20199.1002
/Applications/Rhinoceros 2.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoDLR_Python.rhp “IronPython” 6.28.20199.17132
/Applications/Rhinoceros 2.app/Contents/PlugIns/RhinoRender.rhp “Rhino Render” 6.28.20199.1002
As a quick workaround you can set right-click to be activated when you click the bottom right corner of the trackpad. Maybe that works the same as the right-click of a mouse. It’s in System Preferences -> Trackpad.
Hey,
Using control+click for right click was also reported here recently and is tracked by RH-59829.
Thanks for your feedback!
Apologies for bringing this back from the dead… I can reliably destroy the ability to right click by moving grasshopper to a different monitor from the main rhino window (which would otherwise be very useful).
To be clear, when I say “right click,” I also mean ctrl+click.
I’m on a macbook pro, so here are the two possibilities:
rhino on built-in monitor + grasshopper on secondary monitor = right click works
grasshopper on built-in monitor + rhino on secondary monitor = no right click
grasshopper and rhino on built-in monitor = no right click
grasshopper and rhino on secondary monitor = right click works
tl;dr, right click doesn’t work when gh is on the built-in monitor
macOS 10.15.7, rhino 7.5.21068.13002, 2021-03-09
Just encountered the bug with right click not working in Grasshopper when on secondary monitor 
(macOS Mojave 10.14.6 ). Not sure but might have been introduced in the latest SRC - 7.5.21082.11002, 2021-03-23.
Just to clarify - Rhino i s running on main monitor, Grasshopper on secondary.
As soon as I drag the Grasshopper window to main monitor it works again.
Please look into it as that’s the main workflow for me and probably many others…
Thanks !
@curtisw Indeed - reinstalled the official RC 7.4.21078.01002, 2021-03-19 and the problem disappeared so it seems that the latest SRC introduced this bug unfortunately…
@curtisw - any chance for fix soon ?
Hi - I have the dreaded Mac rightclick fail problem also. looks like after installing the latest versions of both RH6 and RH7, I can’t rightclick on any components and get the context menu. empty rhino file, empty grasshopper file. drop any component on and try rightclicking and nothing happens.
I’m running the latest Catalina.
EDIT: just noticed someone mentioned in the comments above it was only failing on their secondary monitor, and indeed, this is the case for me also. if I move the GH window to the main monitor, it works fine.
Hi @jkozniewski, @Ben4 and @defenestrated.
Thanks for reporting the issue! I have yet to test it but I know of a change that could be the culprit. I’ve created RH-63853 to look into it.
For future reference, creating a new discourse post would be preferable as it shows more prominently for review.
Ah, good to know. Thanks!
uh… so it’s not fixed in latest 7.6 ?
any ETA for fixing this (at least for next SRC ?)
Hey @jkozniewski, this should be fixed in the next 7.6 SRC.