Rockwell Automation FactoryTalk Historian SE ActiveView 3.2 User Guide - Manual (Page 49)

3
●
For Developers: Administering FactoryTalk Historian ActiveView
●
●
●
●
●
41
Guidelines for Building Displays
Abide by the following practices when building a display:
 If you know the size of the FactoryTalk Historian ActiveView control
ahead of time, design the display to keep scaling to a minimum. To
accomplish this, restore the display window in FactoryTalk Historian
ProcessBook and then size the window to match the size of the
ActiveView Control's window. Very large displays that are viewed in
small ActiveView Controls usually do not show as well as smaller
displays.
 You can host more than one control on a page. Consider dividing
dense content into a set of displays.
 For a display to scale well, keep each of the elements within the
display scalable. In particular, use TrueType fonts for PIValues,
PIButtons, PIText, and any ActiveX controls, because they scale well.
 When working with ActiveX controls, text elements on those controls
may not scale exactly. Allow extra space for disproportionately scaled
text by sizing controls to give room for text to grow beyond the
bounds of the original design. For example, make a command button
larger and use a shorter caption string instead of sizing the button to
match the caption's size.
 Select fonts for the Display Document that are likely to be available on
each user's PC. TrueType fonts are preferred because of their
scalability. Your organization may have standards for font use.
 Any embedded ActiveX controls within a Display Document must be
installed separately on every user's PC.
 Embedded ActiveX controls, such as drop-down lists, usually do not
resize well when the Display Document resizes to fit the ActiveView
Control.
 If you include ADO data through PI Data Sets in the Display
Document, ensure that the ODBC data source is configured on each