| Richard,
Is it possible for you to try the same operation - ie Register Entity using
the FCL and let me know if the same truncation occurs in the reply text there.
The string which is being truncated is the reply text which has an FAO expansion
of the unknown entity. If you can do the above in the FCL, it will help
us determine where the error is, in the expansion or in wrapping around the
information. Although the reply text, even when expanded, in this case should
fit on one line.
Do you remember if it looked like more information would fit in the Register
Entity error box - looking at the code, it should allow for 60 characters,
which even the entire string isnt, and the truncated string is less than 35.
Thanks for telling us about this. Let me know about the above.
Verna
|
|
Verna,
FCL displays the full message, that's where I got the full text for .0, I
should have mentioned that.
The field in the box isn't wide enough for 60 chars. If you're using
DECwindows Notes the next reply will show you what it looks like.
|
| Richard,
Thanks for the screen display. If pointed me in the right direction. After
expanding the argument reply text, we neglected to update the length of the
text widget from before fao expansion, where we had
No such entity: <!Unknown Entity>
Thus instead of displaying
No such entity: Archive AIM_NS:.imsym.archive2 Bitfile
the field was truncated to unexpanded size
No such entity: Archive AIM_NS:.i
Will be fixed for V1.1 EFT.
Thanks,
Verna
|