Enabling or disabling the persistence of a control in a window

1. Open the control description window.
2. On the "Details" tab, check (or uncheck) "Store the value".

• In Android, the persistent values are saved in the Shared Preferences of the application.
• In iOS, the persistent values are stored in the parameters of the application ("NSUserDefault").

Remark: This mechanism can be set up by the user using the "Store" in the context menu of the controls (AAF) option..

Studying the operating mode

• The content of the control is strored when closing the application.
  This information is stored in the registry, in the following key: "HKEY_CURRENT_USER\Software\<Company>\<Project Name>". This key is returned through programming by ProjectInfo.
• During the next application start, the persistence mechanism restores the stored controls in their previous status. This restore operation is performed between the declaration code of the window and the initialization code of the window.

1. Value defined in the "Content" tab of the control description.
2. Running the initialization code of the control. This code can initialize and modify the initial value of the control.
3. Persistent value (saved in the registry, in a parameter file, ...). If a persistent value was defined for the control, this value is assigned to the control.
4. Running the initialization code of window. This code can initialize and modify the value assigned to the control.

• the processes for modifying the controls "automatically" assigned are run.
• the selection codes of List Box and Combo Box controls are run.If the process for modifying or selecting the control must not be run, its execution can be conditioned as follows:

// Code de sélection d'une ligne d'un champ Combo 
// ou code de modification d'un champ
IF OPENING THEN RETURN

Setting

• The method for storing the data:
  • Document in XML format (not available in Mobile version).
  • Configuration file (.ini).
  • Registry.
  • String in XML format (to be sent by socket or HTTP protocol for example).
• The location corresponding to the method specified in the first parameter (path of XML document, path in the registry or path of configuration file).

// Utilisation d'un fichier de configuration (.ini)
InitParameter(paramIni, "C:\temp\MaConfig.ini")

Storing the global variables of a project

Implementation

• The name of the parameter to restore (logical name), for example the name of the corresponding variable.
• The default value of the parameter (if this parameter has never been saved or used).

// Chargement d'un paramètre de type entier
gnNbLancement = LoadParameter(CS_NB_LANCEMENT)
// Chargement d'un paramètre de type date
gdDateDernierLancement = LoadParameter(CS_DATE_LANCEMENT)
// Chargement d'un paramètre de type heure
ghHeureDernierLancement = LoadParameter(CS_HEURE_LANCEMENT)

• The name of the parameter to save (logical name). This name is used in LoadParameter.
• The parameter value.

// Mémorisation d'un paramètre de type entier
SaveParameter(CS_NB_LANCEMENT, gnNbLancement)
// Mémorisation d'un paramètre de type date
SaveParameter(CS_DATE_LANCEMENT, gdDateDernierLancement)
// Mémorisation d'un paramètre de type heure
SaveParameter(CS_HEURE_LANCEMENT, ghHeureDernierLancement)

Storing the global variables of a project

1. During the first startup, the controls have no stored value, the operating mode is "as usual".
2. At the end of the application, the persistence mechanism stores the search criteria selected by the user.
3. When starting the application, the stored controls are restored and the modification codes of controls are run.
4. If these modification codes trigger the execution of the search (common case for a radio button), the search will be performed with different criteria for each stored control! This operation can be very long according to the searches performed.

Optimization

1. Declaring a global window variable (boolean type) in the relevant window.
   

   // Code de déclaration de la fenêtre
   GLOBAL
   gbRestaurationEnCours is boolean

2. Initializing this variable to "True" in the declaration code of the window.
   

   // Code de déclaration de la fenêtre
   gbRestaurationEnCours = True

3. Adding a test on this variable in the potentially long processes. If this variable is positioned to "True", the process is not performed (the controls are currently restored by the persistence mechanism).
   

   // Traitement potentiellement long
   IF gbRestaurationEnCours = True THEN RETURN
   ...

4. Assigning this variable to "False" at the beginning of the initialization code of the window to restore the standard operating mode of the application.
   

   // Code d'initialisation de la fenêtre
   gbRestaurationEnCours = False