4D v16Windows and navigation |
||
|
4D v16
Windows and navigation
Windows and navigation
In addition to the manipulations explained in the video, you should also note that: 4D 4D uses the ALERT command to display messages. You’ll quickly notice that it is often necessary to update messages with additional information. Keeping in mind future applications, you will set up a customizable form that will replace the ALERT command and display more personalized messages, where you may (or may not) authorize the copying of error messages. Also remember that this alert dialog is a separate form. So it can contain:
You can even send an automatic e-mail to the Help service containing the following information:
You can also set up the form so that:
Once you get the hang of it, the sky is the limit. In this video, we're going to learn how to use the automatic sizing properties of objects and to understand the possible interaction between programming and interface management. After touching up the interventions form and the table a little by adding descriptive text, comments, the % completed, an ID, and so on, we now want to include a button for sending e-mails in the detail form of the Interventions table. This e-mail will be sent to the technician in charge of the intervention. To do this, we need to add this button and the e-mail input interface. We have created a MAIL project form as well as a DETAIL_FUNCTIONS method that we will call to Cancel or Validate a dialog. So all the form areas will be variables that we can fill with the contents of the fields from one table or another. Let’s make the areas auto-adjustable:
We now need to indicate the type for these variables. Place these lines of code in the form method: $evt:=Form event This lets us initialize the variables we're going to use. We check that the On Load event of the form is the only one checked. The button for sending an e-mail which we'll program later come from the picture library; it's the "Mail" button that is found in the PNG files provided with the example database.
//set a value for the variable to make input easier les variables pour faciliter la saisie
Now let's see whether this dialog box works. We see that the Technician button is in the middle of the comment since the comment is auto-adjustable but not the button. So we're going to fix this by indicating in the button properties that it must move vertically when the form size is modified. Let's check again: the button now moves according to the window size. We're going to trace the method of this button:
We find:
|
PROPERTIES
Product: 4D
HISTORY
ARTICLE USAGE
Self-training ( 4D v16) |