📄️ Info windows
USoft generates an info window for each table that you define in USoft Definer. An info window is simply a Windows form that allows users to query and manipulate data in the table:
📄️ Lookup windows
Lookup windows are meant to be used for stepping out, from a foreign key field in a child table, to a list of possible parent values. The user can choose a (different) )value from the list and return to the foreign key field.
📄️ Related windows
Related windows allow users to navigate, from parent data, to child tables with related data.
📄️ Subtype windows
Subtype windows allow users to step out, from a subtype button, to a window where the user can specify values for subtype columns.
📄️ Secondary windows
Secondary windows are not strictly part of the GUI that USoft generates on the basis of the data model, and they are not strictly necessary.
📄️ Info Box classes
The data forms in the windows of a USoft Windows application are made up of info box classes.
📄️ Underlying queries of info boxes
An info box has an underlying query. It has an object called "query" that has a property Underlying Query. The value of this property is a SQL statement that determines what data is shown in the info box.
📄️ Joined Columns
What is a joined column?
📄️ Extra Queries
In addition to data retrieved by its main query, an info box may show data from extra queries. There are many use cases for extra queries. Here are two examples:
📄️ Class hierarchy of info boxes
The default classes exist in a class hierarchy, in which each subclass inherits all the properties of their parent (their superclass).
📄️ Property Sheets
Property sheets show general information about the Application and GUI classes.
📄️ Windows
This help topic is about windows as a technical object: a container of info boxes and other controls.
📄️ Dialogs
A dialog is a window that helps an end user perform a specific task, or communicates with the user about some specific issue that has arisen.
📄️ Window Sets
You can group info box classes and dialog classes into a window set. You would typically group and list only those classes which are actually used in the application being developed. This enables you to concentrate on the particular windows and dialogs that you are designing.