Hi there,
in a new model, when I create a text object and subsequently or later on modify it’s height to a different value, rhino goes south when the decimal delimiter in this field is a comma instead of a point. The moment focus leaves that field and it’s new content gets evaluated, the crash takes place, no matter which way I go to Object Properties.
This case might sound very minor, but I’ve lost quite some unsaved changes on this over time, when accidentally used the wrong one. This trap is very tempting, because in my country a comma is the correct delimiter for this. It’s sort of hard-coded in my brain. Moreover, rhino itself handles a comma correctly when typing new float values into gumball’s fields (click on arrow). There, 9,5 and 9.5 are handled equally. Unluckily, comma and point keys are close neighbors on keyboards …
Latest tests on this I did with 5A701, my OS X still is 10.10.1.
