Quote:
Originally Posted by kbs666
we are.
Each view has its own left pane.
|
If by "view" you mean each defined "View" that filters the contents shown, that's not correct. If by "view" you mean that each TAB has its own "left pane", that is correct.
Two tabs using the same View (filtered set of topics) can have different collapsed/expanded elements in the "left pane" (Navigation pane).
The tabs are stored from session to session.
If you have 10 tabs open while running a game, and close RealmWorks. what tabs were open and what was in each tab, and which View was applied to each tab is stored.
So storing the collapsed/expanded state for each of potentially thousands of entries once per tab becomes the problem... startup time can be slow as it is, and this would make it much slower to load the Realm. Shutdown time can also be slow as it is, and this would also make that much slower.
Because that state is stored while RealmWorks is running, using a lot of tabs can make it slow to switch from one to another... that's the effect of "remembering" the expanded/collapsed state for each tab.
Part of the problem, I think, is that people are used to the "Explorer" style, where the left-hand pane is a common "master" for the content in the main window. In typical "Explorer" style setups, there is only one "Explorer" pane, and only one "Content" pane. So clicking on something (such as a file folder/directory) in the left pane causes the content in the right pane to change. In RealmWorks, the "Navigation pane" is not part of the tab, but its contents are determined by the tab... and then it changes the tab's main content pane as the user clicks on something in the navigation.
Changing the appearance of the Navigation pane ... making it more visually part of the tab, for example... might help with making that relationship clearer.. certainly, even something like making its controls at the top not align with the controls for the main view would make it visually clearer that it is subordinate to the tab rather than the other way around. But that would not help with storing the collapsed/expanded state.
It may be that because it LOOKS like the Explorer style that people are used to, it needs to BECOME that style...at which point, storing which View is used and the collapsed/expanded state may become more practical.