| | Known Issues
Table Widget Editor |
|
>
> |
- Some planned features are not yet implemented:
|
| |
- There is no spec to enable/disable multi-select
- There is no option to require that at least one record be selected by the user at runtime.
- There is no way to specify a child constraint for a table source process. This means that all of the records in the PCF must be read each time the table is populated.
- There is no ability to specify GUI options for column fields.
|
|
<
< |
- There should be separate event points for Post Read, Pre-Select, and Pre-Display
|
>
> |
-
- There should be an event point for Pre-Display
|
| |
- There should be an option intercept event point with the ability to intercept table events such as click, double-click, etc.
- There is no option to specify which column the table should be sorted on when initially displayed.
- There is no option to define column headings and their GUI attributes. Column heading text is taken from the data dictionary definition of the field.
|
|
<
< |
- There is no option to specify that a field (column) should perform a data lookup. Consequently, there is no option to have a data lookup populate columns for fields from other files.
|
>
> |
-
- There is no option to specify that a field (column) should perform a data lookup. Consequently, ILF code must be used in the Post PCF Read event point to manually retrieve data.
|
| |
Table Resource Editor
Table Widget Runtime
- The table widget is only suitable for displaying a relatively small number of records. Otherwise, the time needed to download the records to the client can get excessive. Records can only be loaded at a rate of about 2,000 records per second. Consequently, the table widget probably cannot be used as a record selector for larger records sets. For example, the time needed to load about 30,000 records is about 15 seconds.
|
|
<
< |
- The table widget is always repopulated when returning from an optional child process. This can cause long pauses if the number of records included in the table is more than a couple of thousand.
|
| |
- Appx navigation keys take priority when in the Table Widget. Any key that would set --- OPTION (eg, Page Up/Page Down) will be returned to your input process and will not affect the table widget. Other keys, such as cursor up/down, can be used to navigate in the Table Widget.
|
|
<
< |
- Columns sort based on the displayed value in a column, not the field values. For example, dates displayed as mm/dd/yy will not sort in date order.
- At runtime, a table widget never seems to keep the focus. When you select a record, the focus returns to the field which had the focus before you clicked to select a record.
|
>
> |
- Date columns sort based on the displayed value, not the actual date. For example, dates displayed as mm/dd/yy will not sort in date order.
|
| |
- At runtime, you cannot click on a row to select it unless all modifiable fields on the screen have satisfied the hard edits which are enforced by the engine. For example, an invalid character in a numeric field on the same screen will prevent you from selecting a record.
Drag & Drop Runtime |
| |
- The other functionality described in feature 44 has not been implemented
Option Numbers in Design Mode
- Option numbers are now displayed on buttons on the image editor if Show Option Numbers is turned on. But, there is no toolbar button or pulldown menu option to turn it on or off. It must be turned on or off by using the right-click menu. Better than nothing but not obvious.
|
|
<
< | Other
- Need .WIDGET routine to REFRESH Table Widget via WIDGET VISIBLE INIT, maybe?. * Fixed * Now have field --- WIDGET RELOAD DATASRC as a widget field that if set to Y in Option Intercept will cause the Table widget to reload it's content even though it may not go to Pre-Display. There is also a new subroutine called .WIDGET RELOAD DATASRC that if passed a Widget Name will set the field with much less ILF code needed. You can also pass it two widget names and it will BEG AT and END AT on the two names and set all the widgets it finds.
|
>
> | |
| |
Comments: |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.