Navigation
Last updated
Last updated
The navigator concept brings together a few elements: left/right arrows in the ribbon and a left pane grid showing the values of the primary key of the module (PK must be edited via a xTextBoxSearch, the so called âmainâ xTextBoxSearch).
For the navigation to work properly, the property AutoNavigate (in XAML) should be activated. Navigator also binds itself (as a control, visually) to the main xDocTab of the window, hence a window that doesnât have a xDocTab canât display the navigator.
If the data inside of a module is being retrieved based on a âmainâ xTextBoxSearch, it can be registered in the xaml designer as following:
When the âNavigator SearchBoxâ setting is activated, additional functionality can be integrated automatically:
AutoRetrieve triggers an ItemChanged event automatically when the user opens the module from the module shortcut (âGo toâ) TextBox (e.g. âSK AXIMAâ). It simulates a user input in the Main TextBoxSearch and does a retrieve based on the detected value.
AutoNavigate triggers an ItemChanged event automatically inside the âNavigateBackâ / âNavigateForwardâ methods. It uses the sql of the SearchDef (xTextBoxSearch) to find the next/previous value and it also implements circular retrieve (forward action on last item goes to first, back action on first item goes to last).
If the data inside of a module is not being retrieved based on a âmainâ xTextBoxSearch, the behavior of the retrieve action needs to be programmatically specified.