Thanks, Bernhard. Here are my results.
Using ribbon.Visible = false worked in terms of making the ribbon not visible, but the top of whichever container/control is docked below the ribbon still extends to the top of the form border. So, if I put a Button control at the top
of a panel and then set the dockStyle of the panel to fill, after calling ribbon.Visible = false the Panel seems to fall out of the client area and the Button within the Panel gets hidden underneath the top of the form border.
Using ribbon.Viewable = false seemed to produce the expected result. After calling ribbon.Viewable = false with a Panel docked below the ribbon with its dockStyle set to Fill, the ribbon disappeared and the Panel remained inside the
client area and all child controls of the panel remained completely visible.
Problem solved. so it seemed...
So, it seemed my problem was solved with ribbon.Viewable. However, I thought I would try the updated Ribbon.cs (windowsribbon-56090), and now…
ribbon.hide produces the same result as ribbon.visible, which is any docked container or control below the ribbon falls out of the client area underneath the top of the form border.
ribbon.visible = false has the same result (no change), which is any docked container or control below the ribbon falls out of the client area underneath the top of the form border.
ribbon.viewable = false
seems to no longer exist. In fact, when I try building sample application #15 (ContextPopup), it fails in the form load event when “_ribbon.Viewable = False” is called. It says “‘Viewable’
is not a member of RibbonLib.Ribbon”.
Now I’m concerned. ribbon.Viewable = false was the only thing that worked, but now with the updated source code, it doesn’t work…
By the way, the workaround for the minimizing/maximizing problem seems to be fine in the new source code. Thanks again.