From time to time, text in a layout that was fine when entered suddenly ends up missing groups of characters. In most but not all instances, upper case characters are retained but lower case disappear. Changing the font rectifies the problem but it is disconcerting when this happens because one does not think to re-check elements that were fine when created and received no changes afterward.
Hi JC1-
Sorry for the delayed reply.
Rhino 5 is getting rather old and our ability to make changes to fix bugs, especially in response to changes and updates in macOS has diminished to zero. What version of macOS are you running?
If you are seeing the same behavior in Rhino 7 for Mac, we would request that you provide your SystemInfo (this command is only supported in Rhino 6 and beyond), along with the 3dm file that is giving you trouble.
Best,
-Dan
Hi Dan,
I do understand that Rhino’s human resources don’t extend to fixing bugs in legacy versions of the software. I don’t know if the error reproduces in v7, which I have been trialling, as I couldn’t pin down the conditions under which it occurs in 5.5.5. It appears to be random. Unfortunately, I didn’t keep versions of the models I was working on that produced the error after I had fixed the problem by changing the font.
I am not sure if I am going to pay to upgrade to v7 because one or two bugs that cost me lots of time and effort in v5 for mac never got fixed even when this was the latest version. In particular, the failure of Esc to abort certain types of operation forced me to quit Rhino and lose all of my work on many occasions. This really got to me. Others complained about this and I added my support but the response given was the same as you give below that bugs which don’t appear to affect a lot of users aren’t prioritized. I feel confident that a lot of users did encounter this problem but simply accepted the loss and redid their work without reporting. Indeed, I never send in the report log when an operation fails because all of the work I do is bound by confidentiality, thus my only avenue to bring a problem to light is to raise it on the Rhino forum without disclosing proprietary details.
OK, that’s my gripe.
On the positive side, I very much like many aspects of Rhino and realise that bugs in software of Rhino’s sophistication are not always easy to pin down and fix. On the personal side, Pascal Golay has been very helpful to me on several occasions when responding to queries sent in via the forum.
Kind regards,
John