Example — customized Px view for Hardware Scan Service
In this example, the controller image (NpmHdwView.png) was copied from the platHwScanNpm module and then edited in a graphics program to change the color of the callout arrows
and numbers from the default green to blue. The edited png file is then copied to the controller’s station folder (using the
platform File Transfer Client view), and then referenced in the BoundLabel widget for it in the Px view.
Figure 81. Example customized Px view for Hardware Scan Service
The OptionCardWidgets used in the “side view” positions (topView=false) had formatPalette child properties for borderColor and referenceColor changed from (the default) green to blue, to match the edited image callout lines. (The color of these callout lines and
border is set in the widgets).
In the same way, properties were edited for the HardwareScanServiceReferenceTable widget, including reducing columnGap and rowGap from 3.0 to 2.0. Also this widget’s formatPalette had its child property for referenceColor set from (the default) green to blue, and properties referenceBackgroundColor and dataBackgroundColor were set from (default) white to colors cyan and peach, respectively.
Finally in this example, the BoundLabel widgets for “Platform:” and “Host:” near the top of the view had text property edits, to read (instead) “Controller:” and “IP:”, and all three BoundLabel widgets were repositioned and reduced in font size from 14pt to 12pt.
platHwScanType modules (for the appropriate controller type), then pasting that in as the source XML for your new Px view. Using this as
a starting point, you can then use the Px Editor to make tweaks in widget properties, and/or reference images outside of the
platHwScanType modules. Combined with changes in lexicons for the platHwScan modules, this can provide a branded view of the Hardware Scan Service information.