Two new modes have been added to the KryptonNavigator that show the available pages as a set of stacked check buttons.
Stack – CheckButton – Group
This mode presents a single check button per visible page and shows then stacked within a group container. In the example below you can see the client area of the selected page in the middle of the control, below the currently selected check button entry.
Use the StackOrientation property to switch to a horizontal stack instead of the default vertical arrangement.
Use the StackAlignment property to determine where the check buttons are positioned. The first two pictures used the default setting of Center, where the check buttons appear either before or after the selected entry depending on their position in the pages collection.
If you choose an alignment of Far then all the check buttons are placed at the far end of the container and the selected client area always placed at the top, like so.
Using an alignment of Near would reverse this so all the check buttons are at the top and the selected client area is always at the bottom.
Stack – CheckButton – HeaderGroup
This modes combines a header group as the container and places the stack inside the inner area.
You can play around with the header group settings. Here we have the primary header on the left side and the secondary header hidden. The close and context buttons have also been removed from display.
Feedback
There is a design decision I would appreciate feedback on. If there are too many check buttons for the client area then what would you expect to happen with the display?
Would you except a scrollbar to appear so the user can scroll up and down to the check buttons that cannot be seen? Or some other action to occur?
