The @@self, @@parent, and @@ancestor[n] keywords for localsim:property tags are supported in GraphWorX64. The syntax for these keywords was chosen to match that of AssetWorX.
localsim:property:@@self.PropertyPath : self is the dynamic or visual on which the tag is used.
localsim:property:@@parent.PropertyPath : if the tag is on a dynamic, parent is the visual on which the dynamic is attached; if the tag is on a visual, parent is the parent visual of that visual.
localsim:property:@@ancestor[n].PropertyPath : where ancestor[0] is self, ancestor[1] is parent, ancestor[2] is parent of parent, etc.
The example display attached to this work item demonstrates a variety of usages of these keywords.
The @@self, @@parent, and @@ancestor[n] keywords for localsim:property tags are currently supported in WPF, UWP, and HTML5.
Examples in GraphWorX64 - Configuration Mode
Example in GraphWorX64 - Runtime Mode
Relative references are special placeholders that refer to the current Equipment, and they get replaced through the Runtime by their full point names or by the values of those points.
There will be these relative referen ces:
@@self
@@parent
@@ancestor[n] - @@ancestor[0] equals to @@self
Example: An Equipment Property, which Sums Together the Values of Two Sibling Properties (Named a and b)
Example: An Equipment Description, which Uses the Value of its Own Parent’s Display Name
Example: An Equipment Command, which Sets the Value of a Global Alias to the Path of the Current Equipment
Relative References are applicable to all text fields (except for the Name, Custom Identifier and except where Runtime Parameters do not apply on Equipment Properties).
All placeholder replacement is static and happens only when the configuration is loaded or changed.
@@self (and the other placeholders) are replaced by the point name of the current equipment (not prefixed by node name). This makes them usable whenever a point name is expected (for example in expressions).
When further enclosed by << and >>, the Asset Catalog will replace them with their static value.
<< and >> can get the value of a static Equipment Property or the value of attributes on both Equipment and Properties.
There is a browser for Relative References, integrated into the Data Browser where applicable. They are also available in many command fields, but not in all, due to technical reasons. Relative references also work on command text fields which do not show this browser (except for the command Name).
Data Browser Support for Relative References
See Also: