| |
| META TOPICPARENT |
name="APPX520Features" |
New Table Widget |
| |
When the Input process executes, after the Pre-Display event point runs, the Table Widget(s) will be loaded. Each Table Widget will execute the Event Points in the Table Source process as described above. |
|
<
< | If you have specified an Option for either the Single click or Double Click actions, then those Options will fire when the user clicks a row. This is no different than the user clicking a button that fires an Option, so the Option Intercept event point will execute first. If --- OPTION still contains the USER XX value after the Option Intercept event point ends, then Appx will continue it's normal processing, i.e., it will attempt to run the specified Optional Child, then re-execute the normal event points for the image, including Pre-Display. This means your Table Widget will be re-executed as well, and the data reloaded. If you do not want this to happen, you should set --- OPTION to blank in the Option Intercept Event Point. Conversely, if you want the Table Widget to reload, but do not want all the other Event Points in the Input process to fire, you can read the --- WIDGET record for the Table Widget and set the --- WIDGET VISIBLE INIT field to Y, then rewrite the WIDGET. Then set --- OPTION to blank. Since --- OPTION is blank, no other event points will execute, and since --- WIDGET VISIBLE INIT was set to Y, the Table Widget will re-execute. |
>
> | If you have specified an Option for either the Single click or Double Click actions, then those Options will fire when the user clicks a row. This is no different than the user clicking a button that fires an Option, so the Option Intercept event point will execute first. If --- OPTION still contains the USER XX value after the Option Intercept event point ends, then Appx will continue it's normal processing, i.e., it will attempt to run the specified Optional Child, then re-execute the normal event points for the image, including Pre-Display. This means your Table Widget will be re-executed as well, and the data reloaded. If you do not want this to happen, you should set --- OPTION to blank in the Option Intercept Event Point. Conversely, if you want the Table Widget to reload, but do not want all the other Event Points in the Input process to fire, you can read the --- WIDGET record for the Table Widget and set the --- WIDGET VISIBLE INIT field to Y, then rewrite the WIDGET. Then set --- OPTION to blank. Since --- OPTION is blank, no other event points will execute, and since --- WIDGET VISIBLE INIT was set to Y, the Table Widget will re-execute. You can also use the REFRESH command to force Appx to refresh the widget under circumstances where it would not normally do so automatically, i.e., if you update the data and then directly invoke another process via in INPUT command. In that case, unless you issue a REFRESH, the old Table Widget data will remain on the image. |
| |
Note that if you do not set an Option to fire when the user selects a row or rows, you will need some other method for the user to signal that they are done selecting rows. For example, you could put another button on the image that they click. You can test for that Option, and if true, examine the --- SLCTKEYS memory file to see which keys were selected. |
| |
The --- SLCTKEYS PCF KEY VAL field is an alpha field that may contain binary characters if the PCF Primary key is a numeric field. In this case, you cannot simply move the --- SLCTKEYS PCF KEY VAL field to the numeric field, you need to have a group field that contains the numeric field and move --- SLCTKEYS PCF KEY VAL to that field. |
|
>
> |
The user can click a column heading to sort the data in ascending or descending order, and they can drag the columns to re-arrange them. These changes will remain until the process is restarted, at which point the widget will revert to the designer's specifications. |
| | Modify via ILF |
|
>
> | You can also create or modify the Table Widget via ILF code. The fields unique to the Table Widget are:
- WIDGET WIDGET TYPE - must be TABLE
- WIDGET D SRC AP - The Application ID of the Table Resource
- WIDGET D SRC NAME - The process name of the Table Resource
- WIDGET D SRC INV TYPE - The invocation type of the Table Resource process
- WIDGET OPTION - The option to fire on a single click
- WIDGET OPTION 2 - The option to fire on a double click
|
| | Comments:
Read what other users have said about this page or add your own comments. |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.