I also would like to report one UI BUG (at least I consider it that way) which could be resolved super quickly by the programmers at “McNeel” in the next Rhino 7 SR update. It’s the extra, unwanted space in the Command line that destroys the visible portion of the text field after using the _PolygonCount command. Some other commands also cause that mess for no reason. Here is an example showing how the bug basically makes the user experience bad:
There are 15ﾠ269 quadrilateral polygons and 34ﾠ374 triangular polygons in this selection
There would be 64ﾠ912 total triangular polygons in this selection after forced triangulation
Here is how the Command line looks like before running the _PolygonCount command:
Strange things happen. When I switched to Segoe UI, the font size slightly increase and looks like calculating the render mesh of a box is fine, but doing so with the render mesh of a sphere added a blank space… Both were just built in a new scene sitting next to each other.
My Windows 10 is English US but set to use Bulgarian metric system. In Bulgaria we don’t write 18,752. We write 18 752 instead, adding a blank space between every 3 digits from backwards. I wonder why Rhino adds a free space between the two sentences…
Yes, most likely that’s the issue as you find out above. The same numbering order is also used in a variety of other countries other than Bulgaria, too. Here, we use a decimal comma, this is why we use a space between every 3 digits. For example, 18 752,5 means “eighteen thousand seven hundred fifty-two and five tenths”.
OK, so most likely it will not be fixed for Rhino 7? I reported that bug at least twice since the release of Rhino 7 back in 2020, but instead of resolving it on time by the programmers at “McNeel”, I was advised to increase the height of the command line with two extra rows, which is unacceptable, because it will heavily reduce the working space in the viewports… I’m forced to often click on the Command line and use the arrow keys or the mouse scroll wheel to navigate across the buggy spaced lines there.
I had the impression that the Rhino 7 Service releases that appear after the initial release of the program are updates that fix known bugs while the program is still alive, i.e. not replaced on the market by its successor, the completed Rhino 8. As I mentioned above, I reported that bug at least twice in the previous years, however, it was ignored at the time.
As for Rhino 8 WIP, I tried several of its releases so far and it has way too many disadvantages compared to Rhino 7. I also created a dedicated topic where I wrote my impressions from the Rhino 8 WIP with bugs and other issues that were the most noticeable from my point of view. Rhino 8 WIP from last month still had the majority of those unresolved. I just downloaded the latest WIP and it still has those unnecessary UI elements such like 3 dots on each bar. Some SubD icons are still too dark, despite that I reported that long time ago as an issue for Rhino 7’s UI (maybe last year?). There is a major issue in the latest Rhino 8 WIP with positioning of the Gumball after extruding a surface into a polusurface and then exploding the latter into separate surfaces. That was also reported by multiple people during the entire year 2022.