Components can also be created by simply dragging a Tag onto a container. Depending on the data type of the Tag, you will get a popup menu prompting you to select an appropriate type of component for that Tag. This technique is great for rapid application design as it does two things for you:
- The component is created at the position you dropped it.
- A variety of property bindings are created automatically.
Tags are used in windows to power property bindings on components. The easiest way to make some components that are bound to Tags is to drag and drop some Tags onto your window.

In the example above, we dragged the DayTank Memory Tag onto the window and were given the option of Display, Control, or Templates. Within the display components, we were given the option of displaying the tag in a Numeric Label, LED Display, Multistate Indicator, Progress Bar, or Tank component.
The bindings depend on what kind of Tag was dropped and what kind of component was created. For example, lets suppose you have a Float8 point that represents a setpoint, and you want to set it. Drop the Tag onto a container and choose to control it with a Numeric Text Field. The following bindings will be set up automatically:
- The text field's doubleValue property gets a bidirectional Tag binding to the Tag's Value property.
- The text field's minimum and maximum properties get Tag bindings to the Tag's EngLow and EngHigh properties, respectively.
- The text field's decimalFormat property gets a Tag binding to the Tag's FormatString property.
- The text field's toolTipText property gets a Tag binding to the Tag's Tooltip property.
It is important to realize that multiple property bindings are created when creating components this way. These bindings not only using the Tag's value, but much of the Tag's metadata as well. Using the Tags metadata in this way can greatly improve a project's maintainability. For example, if you decide that the setpoint needs 3 decimal places of precision, you can simply alter the Tag's FormatString to be #,##0.000
, and anywhere you used that Tag will start displaying the correct precision because of the metadata bindings.