Difference: 520NewTableWidget (3 vs. 4)

Revision 42012-07-27 - JeanNeron

Line: 1 to 1

META TOPICPARENT	name="APPX520Features"

New Table Widget

Line: 30 to 30

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.

Changed:

<
<

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.

>
>

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 use the --- .WIDGET RELOAD DATASRC subroutine, then set --- OPTION to blank. Since --- OPTION is blank, no other event points will execute, and since --- WIDGET RELOAD DATASRC was run, the Table Widget will re-execute.

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.

View topic | History: r13 < r12 < r11 < r10 | More topic actions...