Missing feature in Rhino (PLEASE READ)

Nope. Not at all. My normal config is 2 docked panels on the right edge, one over the other, top one holds Properties, Display and BoxEdit tabs, bottom one holds Layers and Notes. In the past, I have had the Layer States tab in the bottom panel, and that is actually a plug-in, but I haven’t had it in there for awhile now.

–Mitch

Just FYI
After last lost of user interface, I have started Rhino as Administrator and rearranged user interface. It has been stable for 6 days.
Today, I have closed and save a Rhino project, restarted the computer, reopened the same project and the user interface was mismatched.

Do you have a customized workspace (your own toolbars, etc?) Do you by any chance have a toolbar docked next to the command line?

–Mitch

Yes, here is my Rhino user interface (the 2 displays on the right)

OK, that makes at least 3 people (including myself) that are experiencing this problem that have posted here, and all of them have at least one toolbar docked next to the command line - and every person has the osnap box as one of the docked toolbars. I’m beginning to suspect docking toolbars next to the command line may the culprit, maybe just the osnap box.

–Mitch

I have this problem from time to time and I have a few toolbars, including the osnap box, docked up there.

I have toolbars next to the command line like you describe but I don’t have problems very often. The last time the toolbars went haywire was after a Windows update and it wanted to restart, I had Rhino running with an unsaved file that stopped Windows shutting down. As soon as I saved the file and closed Rhino Windows shut down but it didn’t give Rhino enough time to finish closing down and saving the layout, the next time I started Rhino the layout was all wrong. I’ve also done this myself, closing Rhino then shutting Windows down too quickly.

Closing Rhino and restarting another instance of Rhino to quickly will mess things up quite consistently, one that catches me out is if Rhino crashes and you and you start Rhino straight away. If you’re lucky and still have another instance of Rhino running with a good layout you can shut down all the other instances of Rhino leaving the good one until last, after shutting the good instance down want a couple of minutes just to make sure it’s saved the good layout then restart.

If you close Rhino it takes quite a while before it’s gone from the task manager, if you close windows or start a new instance before it’s gone from the task manager you will have problems.

Mark

Thanks Mark - do you have the osnap box docked next to the command line? Custom made toolbars? --Mitch

I have osnap above the command line and custom toolbars next to it.

Mark.

OK, if you are not having problems with your config, then I’m homing in on the cause being the osnap box being docked directly next to the command line… Need to hear from more users before the hypothesis is either confirmed or disproved… --Mitch

I don’t have problems with my setup (in RH5 that is) and my osnap box is not docked next to the command line.

EDIT: I quoted the wrong sentence. Here’s the one I meant:

“As soon as I saved the file and closed Rhino Windows shut down but it didn’t give Rhino enough time to finish closing down and saving the layout, the next time I started Rhino the layout was all wrong.”

I have noticed from time to time over the years that when I tell Windows to shut down, a message box will appear that says some process or other is still active and asks me if I still want to shut down or wait until the process ends. Hasn’t happened often enough that I remember the exact details, but it causes me to ask:

Is this something that Windows does automatically for any process that is still active when it’s trying to shut down, or does the process have to somehow tell Windows not to shut down while it’s still active? If the second case, does Rhino let Windows know it shouldn’t shut down while Rhino is still running?

I dock the OSnaps next to the command line, on the right, Filters on the left , all at the top… so far V5 keeps itself together for me… hardly proof, but, just throwing another case on the pile.

-Pascal

All of the above :smile: