mac be damned!

Well, when I say "retina" I'm really just talking about any 5k screen which uses a scaling factor. Running Grasshopper1 on 5120x2880 @ 200% was an absolute nightmare a few weeks ago, but by now I've managed to fix the most important issues. 

Hopefully I won't be starting a flame war, but I raised this same point a few weeks ago in a similar discussion about graphics issues with the development of a slicing program for 3D printing: is the number of MAC users sufficient to justify the expenditure of valuable resources (David's time in this case) for developing and maintaining a MAC version?

Clearly we end users cannot answer this question (the people who know don't tell, and the people who tell don't know), but from a purely business perspective I would hope someone is considering the question.

[...] is the number of MAC users sufficient to justify the expenditure of valuable resources (David's time in this case) for developing and maintaining a MAC version?

Luckily that is not a question we have to answer, because I'm not developing or maintaining a Mac version. Some other McNeel programmers have taken the GH1 source and converted it to Mac, primarily to stress-test the new cross platform UI framework we're adopting in Rhino6 and beyond. When they started it wasn't even clear whether we'd ever release GH1 for Mac, because it might never become mature enough to be shippable. Luckily it turned out to be easier than expected and the port was deemed functional enough to be released publicly.

What I'm doing now (and have been doing for several months) is make GH1 high-resolution ready for Rhino6 on Windows. Since GH1 will be included in the Rhino6 product, and since we're promising that Rhino6 can handle high-resolution screens, these problems had to be addressed. I won't be able to make everything absolutely flawless on high res screens (or rather, nobody wants me to invest the amount of time it would take to get there), but the software needs to be usable.

...but from a purely business perspective I would hope someone is considering the question.

That would be me. There are two parts of the question... is there a short term financial benefit? The answer is "Yes", but it is a bit distracting because supporting two platforms does require cleaning up old code that was developed 10+ years ago.

The second part... is there a long term financial benefit? The answer is "Who knows?" but we do think we will be in much better shape no matter which platform wins... Windows, Mac OS, iOS, cloud* OS, etc.

Hallo David, 

So thanks for OS X this is a nice tool, but maybe you could extend it and also output the limes (german, i think in englisch it is the limit of the function) of the function with n-> +infinity?

This would be very helpfull with other functions as well from time to time...

Richard

Hi Richard, they're not necessarily Gauchy sequences, in fact all the examples in the image above tend to infinity. Note that this is not an analytic evaluator, all I'm doing to replacing [n-?] and [index] and [total] strings with numerical values based on the existing sequence. Essentially I'm just generating a series of numeric expressions that get evaluated one at a time.

Hallo David,

do understand how you do it. It was more a whish for some extra functionality in case you are border with UI design again...