PC SOFT

ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

Home | Sign in | English EN
This content has been translated automatically. Click here to view the French version.
  • Overview
  • Memorize the report of ruptures
  • Programming
  • Forcing the storage of breaks
  • Preventing from storing breaks
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Others
Stored procedures
Overview
When the end user works on a complex Table or Looper control with several breaks, he may want to store the current layout: expanded break, collapsed break, ....
Memorize the report of ruptures
To store the status of the current breaks, all you have to do is select "Store the status of breaks" from the popup menu of the rows found in the Table or Looper control. In this case, when closing the current window, the current breaks will be stored in their status (expanded/collapsed). These breaks will be automatically re-applied during the next window opening.
To no longer store the status of the current breaks, all you have to do is select "Store the status of breaks" from the popup menu of the rows found in the Table or Looper control.
Programming

Forcing the storage of breaks

To force the storage of breaks in a Table or Looper control, all you have to do is use AAFExecute associated with the aafSaveBreakStatus constant.
For example:
// Coche par défaut l'option de mémorisation des ruptures
AAFExecute(TABLE_Client, aafSaveBreakStatus)

Preventing from storing breaks

To prevent from storing breaks in a Table or Looper control, all you have to do is use AAFDisable associated with the aafSaveBreakStatus constant.
For example:
// Pas de mémorisation des ruptures
AAFDisable(TABLE_Client, aafSaveBreakStatus)
Minimum version required
  • Version 20
Comments
Click [Add] to post a comment