Difference: 520KnownIssues (22 vs. 23)

Revision 232012-07-06 - JeanNeron

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: 12 to 12
 

Table Source Editor

  • hitting enter in key entry mode does not bring up list. Read First is set, I can't see what the problem is. Child Constraints maybe? * Fixed ***
  • App Id 0LA should display as --- * Fixed ***
Changed:
<
<
  • Can't Browse and then Navigate to hits
>
>
  • Can't Browse and then Navigate to hits or drill down to error location if there are compiler errors
 
  • link from DD does not work * Fixed ***
  • link from DD is not highlighted if table sources exist * Fixed ***
  • when adding fields from other files, warning message refers to 'Post User Selection' EP. * Fixed ***
Line: 27 to 27
 
  • 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. ** Fixed **
  • Wide Columns appear to be truncated. Try to display a 512 character field. ** Fixed **
Added:
>
>
  • If there are compile errors in the Table Source, they are not displayed. Instead the default display for the Table Widget is shown.
 

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.
Line: 46 to 47
 
  • 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.
Changed:
<
<
  • 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.
>
>
  • 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. Update: Now the Tab Out event is fired, but then the cursor is put back in the field I just tabbed out of. If I tab out again, then the Tab Out/Tab In events are 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? * Fixed ***
  • 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 **
Line: 62 to 63
 
  • .UTIL SUBR DELETE does not remove audit history - * Fixed * added call to 0AD PROCESS (REF INT) (DEL) to duplicate processing done when Sub deleted in 0AD.

Better Error/Warning Control Runtime

Changed:
<
<
  • In client preferences, the messageComboRows shows a default of 0, but it seems if there are >8 messages, a scrollbar is added. Default should show as 8?
  • What is the point of --- MESSAGES? How did you see the designer using this? The messages are still all displayed by the client in the status area, so it's not like the designer can replace that with their own display (although they can complement it). * True * It's meant to give the designer access to the messages that are being displayed to the user.
>
>
  • In client preferences, the messageComboRows shows a default of 0, but it seems if there are >8 messages, a scrollbar is added. Default should show as 8? ** Fixed **
  • Transitory messages (like process name during Em compile, restructuring, etc) no longer appear in the status bar.
 

Better HTML Widget

  • VLC option does not work
  • line breaks not honored in javascript viewer
 
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