A very early version of Grasshopper for Mac is available in the RhinoWIP for testing and feedback.
Users of Rhino 5 for Mac have access to the RhinoWIP. The most recent RhinoWIP contains a hidden command called ExplicitHistory the Grasshopper command.
Please post feedback and report bugs (there are many!) in this category.
@Mitch, this should work as long as there are no compiled components from third-party libraries (same as GH on Rhino when the add-on is not installed, though user objects from clusters should work). Please report anything that isn’t working.
Yes, I know. First thing I thought was that McNeel is going down the same road again as they did with first implementing Toucan and then removing it. Then again - what’s in a name?
Is peacock made up of Clusters as User Objects? As long as the .ghuser User Object only relies on default gh components, it should work if it is saved in a definition.
Super mega cool! I opened a bunch of my previous definitions and all worked fine! (well, I’m not doing any really complex stuff…) I also created a couple of things from scratch, all seems to have the same feel as the Windows version…
What I noticed so far:
Since I’m working on a laptop with a single screen - all I have in Mac - it’s pretty annoying to have the EH/GH window disappear behind the main Rhino window if I left click somewhere in the Rhino window… Have to go through the Window menu to get it back, cmd+Tab doesn’t work (even if it did, it’s still annoying). The Windows version stays on top of the Rhino window, even if it’s inactive. I guess some Mac people might think this is a “feature”…
Single backspace key does not delete objects, you have to hit fn+backspace. Backspace alone works to delete in Rhino itself on my Mac, although I have seen some student Macs where it doesn’t.
The numbers in the sliders sometimes get too small or too big when you double click on them to change values.
Oops, just had my first crash, had several definitions open at once, and tried switching from one open definition to another via the menu, boom… Oh… @dan That one looks like it’s repeatable - tried several times…
@stevebaer and Curtis do all the difficult stuff…but it is your code elegantly “transmogrified.” All that rewriting you did years back to base it on RhinoCommon is coming to fruition, and for that we are thankful.
You know how much we love repeatable crashes! Please post steps (in a separate thread)! Which reminds me, I need to go make all the YouTrack issues public viewable. DONE.