|
|
|
|
|
|
|
|
|
|
- Overview
- Remember break state
- Programming
- Forcing the storage of breaks
- Preventing from storing breaks
Storing the breaks in the Table/Looper controls (AAF)
When an end user is working on a complex Table or RepeatString field with many breaks, he may want to memorize the current presentation: unfolded break, folded break, .... To save the state of the current breaks, select "Remember break state" in the context menu of the rows in the Table or Looper control. In this case, when closing the window, the breaks will be saved in their current state (expanded/collapsed). These breaks will be automatically re-applied during the next window opening. To no longer save the state of the current breaks, select "Remember break state" in the context menu of the rows in the Table or Looper control. Forcing the storage of breaks To save the state of the breaks in a Table or Looper control, use AAFExecute with the aafSaveBreakStatus constant. For example: // Checks by default the option for storing breaks
AAFExecute(TABLE_Customer, aafSaveBreakStatus)
Preventing from storing breaks To no longer save the state of the breaks in a Table or Looper control, use AAFDisable with the aafSaveBreakStatus constant. For example: // No storage of breaks
AAFDisable(TABLE_Customer, aafSaveBreakStatus)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|