Our mac dev team spent a lot of time on this, and I personally think they did a great job. Our goal with Rhino for Mac was to create a UI that was familiar to Mac users. This is a fair representation of the 2007 position, but things are and have been changing over the years. The philosophy behind having two different interfaces is highly debatable but that’s just the way it is. The decision to not make a unified interface was taken way back in 2007 and it’s not likely to change. Hope to see some major changes on the Mac side, especially now that we’re going to a new era with the Platforms, all I can say about that is that it doesn’t always apply, certainly when it comes to the a unique, powerful and proven workflow. I’ve been a Mac user for 25 years and I’m well aware of philosophical differences between the Other companies managed to unify the interface with minor reasonable differences, can’t see why not I know there are some platform specific limitations such file system and graphic subsystem butĪs other mentioned, Rhino is a unique experience that should carry over to every platforms. ![]() (I’m sure expert users have many work arounds) ![]() While I can figure out theĭifferences running on a Mac, the workflow is sluggish at best ,when compared to windows as far as I can manage. Watching many online tutorials, I’m getting very envious at windows users. It seems that with Rhino 7 that issue took turn for worse imo. I’ve seen some posts about the subject but no real conclusions or take-aways why such a stark difference.
0 Comments
Leave a Reply. |