Difference between revisions of "ITrack/Master"
m |
|||
Line 13: | Line 13: | ||
* Maintaining any database connections and handling data [[Database#Query|query]] requests. | * Maintaining any database connections and handling data [[Database#Query|query]] requests. | ||
* Opening modules at the user's (or other modules') request and maintaining the open module list (labeled "Open Windows"). | * Opening modules at the user's (or other modules') request and maintaining the open module list (labeled "Open Windows"). | ||
* Loading and displaying [[ | * Loading and displaying [[Menu|menu options]] contained in the current extensions. | ||
===Main Menu=== | ===Main Menu=== |
Revision as of 01:57, 24 February 2009
Master is a common name used to describe the main ITrack window. This is sometimes referred to as ITrack.exe, since that is the extension that it is stored in. Master is the main file for all current ITrack - Inventory Management systems, including ITrack Pro, ITrack Enterprise, and ITrack AX. All other extensions inherently depend on it (and therefore that is omitted from their dependencies on their individual pages).
In ITrack, Master has the following responsibilities (not all of these items are necessarily always employed in all products):
- Reading computer settings (local .ini files)
- Verifying registration information
- Loading and unloading extensions (dll files), including:
- Module Extensions - or extensions that contain one or more modules.
- Utility Extensions - or extensions that contain no interface modules, but contain core or tertiary functionality used by Master or other modules.
- Database Connection Extensions - or extensions that contain knowledge on how to connect to and interact with a Database.
- Third Party Extensions - these extensions are written and maintained by other companies, but are used to support functionality required by ITrack, such as database interaction.
- User Extensions - similar to module or utility extensions, except that they are written by the user (view user extension page for more info on creating user extensions).
- Displaying the login dialog (for those products with user access restriction) and facilitating login/logout functionality.
- Maintaining any database connections and handling data query requests.
- Opening modules at the user's (or other modules') request and maintaining the open module list (labeled "Open Windows").
- Loading and displaying menu options contained in the current extensions.
Main Menu
This list contains all currently loaded modules that the user can navigate directly to. Some modules are hidden and must be launched by another module and therefore do not show up in this list. Each module has a helpful icon to identify it and a unique name. Clicking on a module name will open the module in the main screen area (right side) and add it to the open windows list.
By default, this module list is sorted alphabetically by name, but the sorting order can be modified in the configuration file (host.ini for most products).
Open Windows
This list contains all currently open modules that the user has opened and interacted with. Items in the list are sorted by how recently the user interacted with them (most recently on the top).
To view a screen that is currently hidden (not the top item on the list), click on the name of that module in the list. To close a module you no longer want open, click on that module's name to open it, and hit the lower X button to close it.