About Paths in CloudTest

Property paths in CloudTest are similar to those found in most operating systems. They are set by specifying the starting element. The “root” or “starting point” of the path is specified (e.g. the item to which the path is relative). Additionally, both of the following conventions can be used to define relative paths: “.” and “..” .

For example, the path {%% prop: Message: Message5/msgprop %%} specifies the property “msgprop” in the Message “Message 5”, which was assumed to be in the same container as the current Message. The “Message:” in the middle field specified that a Message’s property was to be found.

In current paths, the middle field specifies the starting point of the path. The obsolete path above can be written as either:

{%% prop: Message: ../Message5/msgprop %%}

Or:

{%% prop: Clip: Message5/msgprop %%}

This second path is made relative to the current Clip by specifying “Clip:” for the middle field. The second example assumes that the Messages are in a Clip, and not a Chain, otherwise “Chain:” is used for the middle field of the ISSE to specify that the path is relative to the current Chain).

The vast majority of ISSEs and property paths entered probably don’t specify any path currently, and those remain unchanged. For example, the following existing path:

{%% prop: Clip: myprop %%}

The path above specifies that the property “myprop” of the current Clip still works the same in this release and does not need to be changed.

The areas affected by this change are:

  • Path syntax.
  • The Scripting method “getItemViaPath” for all item types.
  • The Scripting objects $prop and $sysprop .
  • A “property path” entered for a repeat that involves a property.

Property repeats are specified in the repeats for Tracks or Clips whenever the repeat involves a property (“Repeat By Property”, “PFor Each”, or “While”).

  • Anywhere in the Clip Editor where the “Property Chooser” dialog is used and a custom property path is entered into the edit control at the bottom.

For example, a path for PropSets is shown on the right.



Similarly, in the Message Editor, Property Sets form on the right, the Starting Element is specified from among: Composition, Current Band, Current Track, Current Clip, Current Target, Current Destination, Current Chain, or Current Message.

Based on the specification, the property path field can take a relative path. For example, the following are all equivalent to set one of the current Message's properties, assuming that the property path field’s value is being set from "Message4" in "Clip7":

Starting point, path Message, propname Message, ../Message4/propname Clip, Message4/propname Track, Clip7/Message4/propname

For a more interesting example, to set a property of "Clip7", which you happen to know is in the same Track as the Clip containing this Message, the following are all equivalent:

Starting point, path Track, Clip7/propname Clip, ../Clip7/propname Message, ../../Clip7/propname