| 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.
|
|
> > | |
|
Table Source Editor
- hitting enter in key entry mode does not bring up list (READ FIRST not set?)
|
|
- 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.
|
|
> > | |
|
Table Widget Runtime
- 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 ==================================================================
|
| New Event Points Editor (Tab In/Out/Value Changed)
- Turning on/off any of the three turns them all off/on. The same field name is in all three positions. ** Fixed **
|
|
< < |
- They only show up on the Alpha field GA, should be for any tabable/modifiable field.
|
> > |
- They only show up on the Alpha field GA, should be for any tabbable/modifiable field.
- check online help
|
|
New Event Points Runtime (Tab In/Out/Value Changed)
- 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. The Tab Out event on the first field does not fire, only the Tab In event on the next field fires. Probably needs to fire 2 events, the Tab Out (with --- CURSOR AT FIELD pointing to the field the user is leaving), then again for the Tab In.
|