Forms in the Sales Application

Now that we have given you specific information about resources and forms, it is time to add a few forms to the Sales application. We’ll show you the resource definitions of some of the forms, alerts, and help text. We won’t show you all the code, however, as it would get exceedingly repetitious and not teach you anything new. Most specifically, we won’t show the code to bring up every alert. Furthermore, we won’t cover forms with any important form objects in them; they are covered in the next chapter.

Here are the forms we are now going to add to the Sales application:

Alerts

We implement several alerts and a custom alert.

The Delete Customer form

We implement some buttons and checkboxes, and have a help string that the user can see by tapping the Info button of the dialog box.

In each implementation we show you any definitions or resources (shown in text in PilRC format), and the necessary code.

Eventually we also need to make sure our application navigates between our various forms and dialog boxes correctly. This is taken care of in our AppHandleEvent function, which we cover in the next chapter (after implementing all of our forms).

Alerts

Here are the defines for the alert IDs, the buttons in the Delete Item alert, and the Product Exists alert (these are the alerts that have more than one button):

#define RomIncompatibleAlert 1001 #define DeleteItemAlert 1201 #define DeleteItemOK 0 #define DeleteItemCancel 1 #define NoItemSelectedAlert 1000 #define ...

Get Palm OS Programming, 2nd Edition now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.