Known Issues

Table Widget Editor

should only accept table source inputs (allowed me to enter a file name)
hide font options, as they don't do anything (or use them as a default for the text on the widget)
data source does not display in input sometimes, hard to reproduce. Try start in .DKL/PLO DRAG 'N DROP, Opt Int, then Opt 94 to .DKL/PLO SHELL SELECTED FILE,then A/C .DKL/PLO DETAILS SELECTED FILE, then IE, double click widget. Or Run the input from design: .DKL/PLO DRAG ’N DROP, Drag some files, Close the input, then: - Start in .DKL/PLO DRAG 'N DROP, Opt Int, then Opt 94 to .DKL/PLO SHELL SELECTED FILE,then goto A/C .DKL/PLO DETAILS SELECTED FILE, then Image Editor, double click widget.
Invocation Type s/b required field.

hitting enter in key entry mode does not bring up list (READ FIRST not set?)
accepts invalid occurrence numbers
App Id 0LA should display as ---
Can't Browse and then Navigate to hits
link from DD does not work
link from DD is not highlighted if table sources exist
when adding fields from other files, warning message refers to 'Post User Selection' EP.

trying use a data source with 5K records, got C-assert or Appx crashes (client closes session):
==================================================================
APPX Runtime Error
------------------------------------------------------------------
MODULE: FP.C.1840
PROCESS: 1EX/00/INPUT - VENDOR TABLE TEST
find_citm() - attach failed
==================================================================
double click option difficult to trigger
if a Size is set, data is truncated to that size, even if the user expands the column.
Filling dead space - right now the last column is expanded –if necessary- to create a row that fills the total with of the table, but that sometimes gives trouble in resizing the last column.
Wide Columns appear to be truncated. Try to display a 512 character field.

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 an item. Problem: Some of those widget types do not fire an option, ie, labels, etc.

There are times when it would be nice for the ADC Window to gain focus when an object is dropped on it.
When dragging files over an Appx screen show where you can drop your files (change border or something of the widgets that can accept a drop action). More of a 'nice to have', since the mouse pointer changes when the mouse passes over a drop target.
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.
If you set @SDND=file to only accept files, and the user drops a folder, the option still fires but the --- DROP* files are empty. The option probably should not fire at all in this case, and the mouse pointer should not change (?).
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.
Create unique filenames for the temp file. Now the subject seems to be the name of the tempfile. This gives problems in dropping more items with the same subject.
Possible bug? When files are dragged from Thunderbird & dropped, the temp file seems to be erased almost immediately (there is no opportunity for the Appx process to get it).

If you have 2 fields beside each other, one with Tab Out and one with Tab In, only one event fires when you tab from one to the other.
Two fields on an image. Both with tab in/out set to yes, when you switch from the desktop client to another program, then switch back to the client. Then tab to the next field, no option is fired.
Link tab in/tab out/value changed to a data lookup. This way it is easy to give already existing screens a more direct interaction with the user without redesigning the whole screen. A designer should tell though that the data lookup should be performed per field. If any of the tab in/out/value changed flags are set and there's a DLU, perform the DLU at the same time as the event is fired?
The default value of valueChangedTimer can be set to 300 instead of 1000. Maybe we need some more testing to be done on that to find out what a nice default can be.