Wire properties
Object properties are attributes with the ability to be updated or read from within a wire. Datasource and template object properties can also be assigned.
Object Properties
Known object properties can be queried via an [object:] token or assigned via an <assign> action tag. Several object tags have a distinct set of properties that can be accessed, many of which will affect the on screen representation of the object.
To view the list of assignable properties for each object, refer to the documentation for individual objects. To view the full list of object properties, refer to Wire object properties. The current value of any object property can be read and utilized within an action by using an [object:path.attributename] token. The path can be an alias or a relative path from the actions target.
Template and Datasource Properties
You may also define object properties for a datasource by using [datasource:path.attributename]. Texttemplates can also utilize properties by using [template:path.content]. Content is used to represent the contents of the <texttemplate> tag.
System Properties
These are object properties that exist on a global level and give you the ability to determine information about the device in use for the Wire. Global object properties also exist to determine the xpos and ypos of a user touch on a multi-touch screen. These will be represented as: _RW-touchedex, and _RW-touchedy. These properties are read only and must be accessed for an object by using onmove, onclick, or onclickup, and querying the object properties within the subsequent action.
[file:nameoffile]
When a file name and extension is populated, the system will return a value of yes or no depending on if the file is stored within the resource bundle or not.
Access: Read-only
Value: yes, no
[system:muted]
Determines the state of sound within the Wire.
Access: Read and write
Value: yes, no
[system:network]
Determines whether or not the device is on a network.
Access: Read-only
Value: yes, no
[system:orientation]
Determines the current orientation of the device.
Access: Read-only
Value: portrait, landscape, square
[system:os]
Determines the current operating system installed on the device.
Access: Read-only
Value: OS version number
[system:parseid]
Determines the unique parse installation ID for a parse account. This is used to communicate authentication to parse for Android.
Access: Read-only
Android only
Value: Parse installation ID
[system:pasteboard]
Assign or read a value that is placed on the native clipboard. Contents can then be pasted outside of the wire.
Access: Read and write
Value: Any alphanumeric value
[system:platform]
Determines the current name of the device used (Ex: iPad2).
Access: Read-only
Value: Device name
[system:pushtoken]
Determines the unique device push token. This can be delivered to external push servers.
Access: Read-only
Value: Device push token
[system:uuid]
Creates a unique UUID for the device every time this property is called. You can then use this ID to create a preference to store a unique ID for the device.
Access: Read-only
Value: Returns unique ID number every time the property is called
Extends
None.
Requirements
None.
Sample Code
<textfield name="myfield" alias="FIELD" width="200" height="50" align="center"
background="#ffffff" valign="center" text="one"></textfield>
<image name="button" source="button.png" bottomof="myfield" align="center" margin="20"
onreturnkeypressed="display"></image>
<action name="display">
<alert message="The textfield has a value of [object:FIELD.text]"/>
</action>
Loading...
There was a problem loading this topic