Now that we have all the specific information about form objects, it is time to add many of them and the rest of the forms to the Sales application. We’ll show you the resource definitions of all the forms and form objects and then look at the code.
We cover the forms and the code for them in order of increasing complexity. The following list shows you our order and which types of forms and form objects are implemented in each form.
The new addition is fields, as well as some buttons and checkboxes.
The new items are a label, a pop-up trigger that has a list associated with it, and a Graffiti Shift Indicator. There are also buttons and fields.
The only object in the form is a list.
This form contains a series of pop-up triggers and fields that are associated with them.
In each implementation we show you any definitions, resources (shown in text in PilRC format), and necessary code.
After dealing with these various forms and form objects we also need
to make sure our application navigates between our various forms and
dialog boxes correctly. This is taken care of in our
ApplicationHandleEvent function, which we cover
We have a bunch of resources for the Edit Customer form. Here are the
#define CustomerForm 1300 #define CustomerOKButton 1303 #define CustomerCancelButton 1304 #define CustomerDeleteButton 1305 #define CustomerPrivateCheckbox 1310 #define CustomerNameField ...