Thank you for setting the YT, I hope that a more streamlined process for backing up and transferring the UI will be implemented soon. I previously discussed the issue of fragmented UI controls. Perhaps my explanation in the following post wasn’t clear enough:
To summarize, constructing or rebuilding the desired UI in Rhino now requires visiting several sections of the software. Previously, syncing my UI was a two-step process involving RUI for toolbars and Rhino Options for everything else. I always kept the latest configuration on the cloud for easy access in case of a system reset, reinstallation, or machine replacement.
Now, the process feels more fragmented. Toolbar RUIs are managed separately from Toolbar Icon sizes. The container tabs are handled independently from the container objects or locations. Both Tab and icon sizes are located in the options but lack the ability to save to Rhino options.
Additionally, resizing the icons or tabs doesn’t automatically adjust the containers to match the object sizes.
Also
, the lingering topic of container setting menu icons alongside the grip handles is also being discussed a lot here.
While I appreciate the detailed and adaptable nature of setting up a UI framework theoretically, it’s also important to acknowledge its ability to reflect the varied applications of Rhino users. Although our feedback on the UI might seem belated, it’s worth noting that many of us, myself included, needed time to fully grasp the new UI’s structure. I’m curious to see whether new users will be taken aback by its unique complexity.