|
META TOPICPARENT |
name="WebHome" |
Unicode Test Plan |
|
...
Misc Bugs |
|
< < |
- New debugger does not work, crashes with error when trying to read --- WIDGET. * FIXED * April 24 engine
|
> > |
- New debugger does not work, crashes with error when trying to read --- WIDGET. * FIXED * April 24 engine
|
|
- Old debugger does not display entire contents of national/unicode fields, even though the data is there.
- Process Generation toolbox. I used the toolbox to generate a scrolling input on the file TST BEGUNI, which contains 2 unicode fields, a 10 character key and a 30 character description. The heading size over the description field is incorrect. It should have 30 ='s underneath it, but it only has enough for the word 'Description'. * FIXED* March 28 engine
- Invalid (blank) occurrence number in Image Editor after hitting F11 then attempting to edit Item. ** FIXED ** March 21 engine
- File Management functions (create, restruct, etc) crash with a 'Value Does Not Fit in Mask' error when setting MESSAGE2 MSG TXT into STAT2 MSG. * FIXED * April 24 engine
- Engine should be transcoding when fields are moved, and throwing a runtime error (like numeric overflow) if the encoding of the receiving field does not contain the necessary characters.
|
|
< < |
- The 'Global EPs for Images' is not highlighted when I add code to the global start of frame. None of the EP's in the Global section turn on highlighting when code is entered.
- Cross Reference display is messed up. Do an x-ref on APPEND NORMAL in App TST, then click 'References' to see what I mean.
|
> > |
- The 'Global EPs for Images' is not highlighted when I add code to the global start of frame. None of the EP's in the Global section turn on highlighting when code is entered. * FIXED * rested with April 24 engine, seems to be ok now.
- Cross Reference display is messed up. Do an x-ref on APPEND NORMAL in App TST, then click 'References' to see what I mean. Retested with April 24 engine, better but still different from 4.2.a. In 4.2.a, in the 'Context' column the word RECORD is immediately followed by the frame & image information. In the Unicode version, the word RECORD is followed by many spaces, then the rest of the context.
|
|
- Put the field --- X on an input image, run the process & try to enter data. If you enter '12345', you will get 'Invalid Numeric Value' error. Add a decimal point to the end and it's accepted.
- The ILF editor does not accept valid characters in the 8859-15 character set, ie, the £ symbol exists in 8859-15, but I cannot enter it on an ILF command.
|
|
> > |
- Changing the value of a --- TEMP field in the new debugger during execution seems to corrupt the field.
|
|
Language Translation Support: |