Difference: 520KnownIssues (45 vs. 46)

Revision 462012-09-06 - PeteBrower

Line: 1 to 1
 

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.
Line: 47 to 47
 

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 **
Changed:
<
<
  • They only show up on the Alpha field GA, should be for any tabbable/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. * Fixed * Now fire the Opt Intercept EPs for Tab Out, then Tab In, setting all the CURSOR AT... PDFs appropriately.
Line: 56 to 56
 
  • 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. * Fixed ***
  • 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. ** Fixed **
Changed:
<
<
  • 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.
>
>
  • 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.
 
  • It also seems like performing a shift-tab (going back to the previous field on the screen) does not work when your cursor is in a textfield with multiple rows.

Create Subroutine via ILF

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback