These are “Panels” not “Toolbars”. I think their positions might contained in the settings folder:
C:\Users\your username\AppData\Roaming\McNeel\Rhinoceros\7.0\settings
somewhere inside of settings-Scheme__Default.xml or window_positions-Scheme__Default.xml
(but maybe I’m wrong about that).
Interesting. Yes, I can see that in some of the many posts here regarding toolbars, actually a few times they mean the panels. Apparently it can also be both.
This sounds pretty promising: All toolbars gone again, Toolbar reset doesn't bring back everything
Is that method still used today?
Great, so it’s not just toolbars that are messed up in Rhino, but also the panels. Jesus. Just goes back to: A complete UI overhaul of Rhino would be a much welcomed move
Messing with the registry? On Rhino 5, yes. As Mitch writes, that is stored in the xml files from Rhino 6.
Just to make sure - what does that mean? I don’t see anything wrong in the picture that you provided.
And FWIW, almost everything about toolbars and panels has now been rewritten in Rhino 8. The last few weeks, the macOS side of this has been worked on. There are still a few issues on both Windows and macOS but it’s starting to look promising.
-wim
I only have a screenshot of the default layout it reset it to. Last time I used Rhino I had 2 columns of panels arranged in 2 rows each. This is roughly what it looked like before:
So this xml file can also get reset during a service release update?
Probably a good idea. Still to this day it doesn’t work properly.
People have and keep complaining about this problem for years.
Let’s hope we will eventually get a stable UI.
That would probably be the best feature of version 8 (not a dig at other Rhino 8 features)
Yes, that’s typically something that gets reset pretty much all of the time.
I’ve created a “workspace” as in your latest image in Rhino 8 and will run with that for a while to see how that behaves.
-wim
Why? Like the toolbar layouts, why would you reset the panels after an update? Is there some way to export and later re-import the panel layouts?
No.
-wim
Oh dear. If you are at the state where even the people at McNeel don’t know why something is happening or what part of the code does it, then you know you have too much legacy code.
I have my fingers crossed for Rhino 8, but until we can see McNeel at least ever so slightly shifting towards getting any UX maturity at all, I don’t hold much hope this situation will improve a lot.
So I guess we are still years away from having different layouts (sometimes called aspects in other software), like say one for modelling workflows, another for rendering setups, one for Grasshopper and so on, and being able to easily switch between them and it switches the toolbars, panels, viewports, etc.?
That’s not reassuring at all!
As a developer, I think you simply can’t sell a software that could have this issues every service release.
In my opinion, this is the first bug you should fix.
This is the first thing you should do, before you add new features.
3/10 telephone calls to our support are caused by this problem.
Fix it!
Please!
