Project

General

Profile

Bug #4244

Bad format of displays with AT

Added by Adrian Lungu over 4 years ago. Updated about 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
08/22/2019
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:

History

#1 Updated by Greg Shah over 4 years ago

  • Description updated (diff)

In statements like DISPLAY expression @ field. the conversion does sometimes add either a bad format to the field or multiple formats.respected. It should be also taken in consideration the explicit format when a FrameElement is created, while this overrides the default format defined in the UI class. In addition to this, the format length should be computed accordingly, while there are cases in which the format is correct and the display field is either too short or too long. Cross data types as well should be managed properly, as if the expression and the field do have different data types, either an error is thrown or an incorrect value is printed. Finally, a comprehensive set of tests, with combinations of data types for the expression/field, is required in order to detect a proper fix.

#2 Updated by Greg Shah over 4 years ago

  • Project changed from Bugs to User Interface

#6 Updated by Roger Borrello about 4 years ago

I'd like to see this moved along when 4207a gets into trunk.

Also available in: Atom PDF