| | Known Issues
Table Widget Editor
- should only accept table source inputs (allowed me to enter a file name) * Fixed *, there was no editting on the fields at all. Made AP & Process name required fields.
|
| |
- trying use a data source with 5K records, got C-assert or Appx crashes (client closes session): ** Fixed **
==================================================================
APPX Runtime Error
------------------------------------------------------------------
MODULE: FP.C.1840
PROCESS: 1EX/00/INPUT - VENDOR TABLE TEST
find_citm() - attach failed
==================================================================
- double click option difficult to trigger * fixed * Now using desktop double-click value.
- if a Size is set, data is truncated to that size, even if the user expands the column. ** fixed **
|
|
<
< |
- 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.
|
>
> |
- 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. ** Fixed **
- Wide Columns appear to be truncated. Try to display a 512 character field. ** Fixed **
|
| | 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 an item. Problem: Some of those widget types do not fire an option, ie, labels, etc.
|
| |
- 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. * Fixed * Now fire the Opt Intercept EPs for Tab Out, then Tab In, setting all the CURSOR AT... PDFs appropriately.
|
>
> |
- 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. * Fixed * Now fire the Opt Intercept EPs for Tab Out, then Tab In, setting all the CURSOR AT... PDFs appropriately.
|
| |
- 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.
|
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.