Sometime not that long ago O-B either moved to an MDI-based tab-window implementation or changed something in its existing implementation. As a result, tab window status will be restored randomly. Instead of always opening maximised in the main window, they open as non-maximised about half the time. If that happens, the active tab will take up the entire available space, but background tabs will typically be in some kind of collapsed state that makes them a little hard to see if you switch to them (after maximising the active tab).
I personally have no need for the MDI model given that O-B also supports multiple "regular" windows, so this side-effect is quite annoying. Maybe a (hidden) option could be introduced to force tab windows to maximised (assuming the MDI-based implementation is necessary or desired by others)?
Sometime not that long ago O-B either moved to an MDI-based tab-window implementation or changed something in its existing implementation. As a result, tab window status will be restored randomly. Instead of always opening maximised in the main window, they open as non-maximised about half the time. If that happens, the active tab will take up the entire available space, but background tabs will typically be in some kind of collapsed state that makes them a little hard to see if you switch to them (after maximising the active tab).
I personally have no need for the MDI model given that O-B also supports multiple "regular" windows, so this side-effect is quite annoying. Maybe a (hidden) option could be introduced to force tab windows to maximised (assuming the MDI-based implementation is necessary or desired by others)?