| | Known Issues
Table Widget Editor |
| | Table Resource Editor
Table Widget Runtime |
|
<
< |
- It seems that rewriting an ITEM (HTM VIEWER) to a table doesn’t work anymore. This is the code in OI:
-
SET --- WIDGET NAME = *TBL INF02 READ --- WIDGET HOLD 1 FT 0 BY WIDGET NAME T SET --- WIDGET WIDGET TYPE = TABLE T SET --- WIDGET D SRC AP = OTO T SET --- WIDGET D SRC INV TYPE = SUBPROCESS T SET --- WIDGET D SRC NAME = *TBL INF02 T REWRITE --- WIDGET FAIL 0
- Token fields do not work properly, doesn't display the token text, I get some other character, or the table doesn't display at all.
|
| |
- 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.
|
|
<
< |
- The mouse is the only way to navigate within a table widget. pgup, pgdn, cursor up, cursor dn, etc cannot be used.
|
>
> |
- 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.
- 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 Editor
- There should be a flag on the --- WIDGET spec to indicate if the field can accept a Drop action. This should be available for the following Widget types: button, label, table widget, html viewer, and Window Background. Currently only works for Widgets attached to a field on the image. * Fixed * There is now --- WIDGET DROP TARGET that marks a widget as able to receive a drop action. It also looks at --- WIDGET FI CHOOSE MODE to see what kind of Drop should be supported. --- WIDGET FI CHOOSE MODE has values of ANY, FILE, FOLDER, TREE where ANY is a single file or folder name. Many more widget types now support being a drop target, but still require a field on the image.
|
>
> | |
| | Drag & Drop Runtime |
|
<
< |
- There are times when it would be nice for the ADC Window to gain focus when an object is dropped on it. * Fixed * Client window now gains focus on a drop.
- Provide a runtime API to copy the --- DROP* files to memory versions of those files (MDROP* ?) to make it easier for a designer to save the contents of --- DROP.
- Files dropped remain in the temporary folder forever. They should probably be cleared when the --- DROP* files are initialized. Alternatively, provide a method for the designer to specify a location for dropped files, and the designer will manually clear the directory at login. Is this 'Fixed', now that there is a setting for dropCachePath?
|
>
> |
- It is the designers responsibility to manage the files dropped in dropCachePath, the client will not delete them for you.
- On the Mac, the client does not get the focus after a drop action.
|
| | New Event Points Editor (Tab In/Out/Value Changed)
- They only show up on the Alpha field GA, should be for any tabbable/modifiable field.
|
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.