handling and tests for MEDM widgets

[prjemian]

Define handling and unit testing for reading these MEDM widgets. Check them off once both parts are complete for reading a MEDM widget.

• [x] arc
• [x] bar
• [x] byte
• [x] cartesian plot
• [x] choice button
• [x] composite
• [ ] embedded display
• [x] image
• [x] indicator
• [x] menu
• [x] message button
• [x] meter
• [x] oval
• [x] polygon
• [x] polyline
• [x] rectangle
• [x] related display
• [x] shell command
• [x] strip chart
• [x] text
• [x] text entry
• [x] text update
• [x] valuator
• [x] wheel switch

Also basic attribute and dynamic attribute appear at the file level of some displays, such as std-R3-5-ID_ctrl.adl. There can be more than one basic attribute at the file level. Some contain channel information. Where should these data be placed? Could these be errors in the file?

Also: caServerApp/test.adl has some unusual but allowed .adl structures, probably a torture test for translators such as this

[prjemian]

Did not find example of MEDM embedded display widget in synApps modules. Looking through display screens from APS accelerator, noexamples there either. Since this widget is not in the object palette screen of MEDM Version 3.1.14, deleting this widget from the converter.

Will add a request for example .adl file with embedded display widget.