| | Known Issues
Table Widget Editor
- should only accept table source inputs (allowed me to enter a file name)
|
| |
- 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).
-
|
|
<
< | New Event Points (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.
|
>
> | 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.
-
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.
|
| |
- 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.
|
|
<
< | |
>
> |
- 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.
- 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.
- 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.
|
| | Other
- Can't xref table source process types
- Can't print tech doc for table source types
|
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.