| | 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.
|
| |
- 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.
- When a Tab Out event fires, the --- CURSOR AT FIELD refers to the field the cursor is at now. It should refer to the field that triggered the Tab Out, not the next field it tabbed into. Or to put it another way, the Tab Out event should fire before the cursor moves to the next field. ** Fixed **
|
|
<
< |
- If value changed is set but the user tabs out of the field before valueChangedTimer has expired, the value changed event does not fire. If the user has changed the field, the value changed event should fire when they tab out. If Tab Out is also set, it should fire next.
|
>
> |
- If value changed is set but the user tabs out of the field before valueChangedTimer has expired, the value changed event does not fire. If the user has changed the field, the value changed event should fire when they tab out. If Tab Out is also set, it should fire next. ** Don't think this is a correct implementation **
|
| |
- Setting the flags via ILF on non RAW TEXT widgets does not cause the events to fire. Probably should fire for all modifiable/tabable widgets.
Create Subroutine via ILF |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.