|
|
|
|
|
|
|
|
|
|
- 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 works 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 current break statussimply select the "Memorize break status" option in the context menu of a break in the Table or RepeatString field. 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 stop memorizing the current break statussimply select the "Memorize break status" option in the context menu of a break in the Table or RepeatString field. 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)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|