I was happy to read that Notes was fixed in the latest Release candidate for Rhino 7, however, seems like the bug is still present an nothing have been changed compared to the earlier builds. At least my Rhino 7 does not show the expected improvement.
Version 7 SR28
(7.28.23058.3001, 2023-02-27)
Commercial
I have a question. I already have Rhino SR28 Release candidate 3 (7.28.23058.3001, 2023-02-27) since the last couple of weeks, and just downloaded the latest SR28 which, oddly, has the exact same version number (7.28.23058). It can’t install in the normal way, because it’s literally the same version like the old one, despite that the new version was published 8 hours ago. I tried both, “Repair” and “Modify”, but the bug with Notes is still not resolved. The third option is to uninstall Rhino.
Is there a way to install the latest version of Rhino 7 with supposedly fixed Notes that was published 8 hours ago, without uninstalling my current Rhino 7 and risk losing my settings or some of the custom buttons I created? Does that new version Rhino 7 Service Release 28 for Windows and Mac (7.28.23058) have any actual fixes compared to one from couple of weeks ago that was named Rhino SR28 Release candidate 3 for Windows and Mac (7.28.23058.3001, 2023-02-27)? The only difference I see is that the older one had extra “Release candidate 3” in the name.
I also think that way. It’s basically impossible to install the latest Service release now that I have a previous Service release candidate with same numbering.
Looks like I will just wait for the next Service release to actually see a working fix to Notes. It happens on two occasions:
Switch to another program, then revert to Rhino 7. Strangely, the first time you do that, everything looks fine. But wait! Switch again to another program and go back to Rhino 7. Now the entire inside Notes is automatically selected and focus goes to the very bottom of the selection.
Once you click somewhere inside the text field of Notes, then switch to another program and revert back to Rhino. Same bug again.