I posted this same a month or so ago, can't find the thing.
Someone suggested I use an Asking Inga routine which essentially reset all of my preferences. It worked for a while. I had to re-remember many settings get back where I needed to be, annoying. After just a couple days the ribbon would no longer stay minimized.
Does anyone know how to fix this or any clue as to what might be causing it to no longer work?
Ribbon will minimize, but reverts to full if I change model or file. I could really use that extra inch of monitor. When I first started using the recent GUI "upgrade" thought I might need a third monitor. 10.13.01.01
If the state of the ribbon is not save make sure that you have full read/write permissions to the "prefs" folder.
There is an XML Personal.RibbonState.xml in which the status is stored. The file should be updating when MicroStation is closed.
Thanks for the response. Can you tell me something that might help? Your suggestion doesn't fit the case at all. This is defective behavior, I'd like to be able to dock the ribbon sometimes
Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley
Hi Bob,
In the file David mentioned there is a line that tells the Ribbon to be minimized or not. I would check the value once you noticed the Ribbon opening up. I don't run with it minimized so I don't notice this happening, I can try running minimized and see if happens.
<RibbonMinimizedState>True</RibbonMinimizedState>
~HTH
John.
yep
Well that is a clue. I want to have the ribbon up sometimes, minimized maybe1/3 of the time. I edited the xml to "True", the ribbon stays minimized. If I expand it, save and exit, the file updates but does not change True to False. So it's another workaround for me, I can choose to have Microstation start with ribbon minimized or not. I believe it should save the state I last used. Or not
UGH! I just was able to reproduce your issue. As David stated MSTN only writes to the ribbon xml file on file close. The issue is it reads the RibbonMinimizedState on model open and file change. So to reproduce:
I would guess this is a defect but you should probably file a SR with Bentley to verify.