I’m posting this as a separate item from my previous comments on the UI, because it involves perhaps some more specific procedures/recommendations concerning toolbar layout conversion from earlier versions.
I will now need to start re-creating my custom workspace from V7 and earlier with a lot of custom buttons - but all of them have bitmapped icons and I would like to take advantage of the possibilities offered by the new vector based button images. So I guess I will start from scratch again…
Previously, I used a complete copy of the default workspace as a base to which I added/modified buttons, custom toolbars and the like - so the normal default.rui was never open. Now, it seems like that is no longer the optimal way to do this. Because in V8, the default stuff is still there even if you close all the toolbars. As a matter of fact, default.rui no longer exists as of the latest WIP. Nor any other .rui as fas as I can see, my custom .rui is no longer modified when I close the WIP.
So, I am trying to figure out how this is designed to work now. It seems more like that one simply should add any custom stuff one wants as a separate container and leave the default as-is… In any case there’s no longer a separate .rui file to copy or save elsewhere. This however brings with it some interesting issues - for me at least.
First and foremost, I work with schemes to have Rhino start in the three different languages in which I work/support. I have one scheme each for English, French and German which all open with the bog-standard default workspace - so I can see what the customer sees when they call for support, test for bugs, do demo videos, etc. Then I have a scheme with my personal custom workspace for my own stuff.
The three V7 default schemes all call up the same default.rui located in the usual spot:
This is not a problem currently because I never modify that file.
Now, for V8, the default.rui no longer exists. I leave the default toolbars open I can certainly add my own custom ones separately, no problem there. However, in V7 and earlier, I have also modified some of the original base toolbars, adding items, sometimes flyouts and changing images. The problem as I understand it is that any change I make here will also modify the workspace for all of the other schemes that use the default.
I’m wondering how to work around this… I need to know what changes I make in one scheme will be transferred over to the others so I can avoid destroying the default setup. Also what updating Rhino will do if one has modified any default elements.
It seems that modifications do not carry over to other schemes, so that’s good. I tried copying a couple of buttons in one scheme and the copies did not get applied to another scheme. I also tried changing the button image in one scheme and that did not carry over to another scheme either. So far so good.
What I did notice is that if one changes a button image, one has to close Rhino and re-open it to have the changes take effect. Also if one has several instances open (in the same scheme) the last to close overwrites the change - like currently.