Your comments
You can always create a variable with an alias as a value and populate the target with it. This will allow the targeted actions to be reusable.
In version 1.3 of the engine, we have made enhancements to the alert tag to allow for this. While this isn't quite out, it will be submitted and available soon.
When it does you will have some new attributes to rename the buttons in the alert and trigger actions when you select them.
Here is an example of how that will look:
For now though we have less control over the dismissal of the alert button, so you could try using a sync block to throw your play action like you mentioned above, but move your alert to the end of the sync, that way your resetit action will fire and then the alert will display right after. Let me know if that works better for you?
When it does you will have some new attributes to rename the buttons in the alert and trigger actions when you select them.
Here is an example of how that will look:
<alert message="do you like beans?" buttononetitle="yes" buttononeaction="say-yes" buttontwotitle="no" buttontwoaction="say-no"/>
For now though we have less control over the dismissal of the alert button, so you could try using a sync block to throw your play action like you mentioned above, but move your alert to the end of the sync, that way your resetit action will fire and then the alert will display right after. Let me know if that works better for you?
The best way to share code on the forum is to use html code blocks. Wrap your WIRE examples in < code >< /code > and it should display easily.
As far as your question, you are doing this the way it was designed. Conditional logic must move through a workflow when dealing with multiple objects, so nesting your if statements here is the way to go.
You could do this other ways, but I think you might have the shortest approach here.
Here is another approach that would cause you to do several sets of if statements for each 3 across combination...
As far as your question, you are doing this the way it was designed. Conditional logic must move through a workflow when dealing with multiple objects, so nesting your if statements here is the way to go.
You could do this other ways, but I think you might have the shortest approach here.
Here is another approach that would cause you to do several sets of if statements for each 3 across combination...
<if lhs="[var:cur1]" operator="e" rhs="X">
<if lhs="[var:cur2]" operator="e" rhs="X">
<if lhs="[var:cur3]" operator="e" rhs="X">
<alert message="You Win!"/>
</if>
</if>
</if>
<if lhs="[var:cur1]" operator="e" rhs="O">
<if lhs="[var:cur2]" operator="e" rhs="O">
<if lhs="[var:cur3]" operator="e" rhs="O">
<alert message="You Win!"/>
</if>
</if>
</if>
Bryan,
The tutorial does use the alignment tag in step 2 when you wrap your text tag in a panel tag for placement in the PDF.
Can you give me some more detail on where you were having trouble?
The tutorial does use the alignment tag in step 2 when you wrap your text tag in a panel tag for placement in the PDF.
Can you give me some more detail on where you were having trouble?
I will need to clarify this further in the documentation as it reads a little funny.
All locally used datasources need to contain "res://" as a prefix in order to call. So in your case, it needs to be:
Also your xml file needs to be stored at the root for the code above to be valid.
All locally used datasources need to contain "res://" as a prefix in order to call. So in your case, it needs to be:
<datasource name="economistxml" source="res://economist.xml" providertype="xml" query="//item" />
Also your xml file needs to be stored at the root for the code above to be valid.
Currently this is not available within the beta, though it is on our roadmap to complete soon.
I would suggest you pull down your assets and WIRE files through FTPS and upload to another App. You will have to redo your App settings for the new App.
I would suggest you pull down your assets and WIRE files through FTPS and upload to another App. You will have to redo your App settings for the new App.
If not, email me at community@rarewire.com and I will get some invites sent to the email addresses you need.
Sorry for the issues.
Sorry for the issues.
Has he checked his spam folder by chance? Let me know, I have found a bug ticket logged for this, I am following up to see if it has been pushed to release.
I would recommend uploading this content using FTPS access and a good text editor as it is a good 600 MB worth of images, etc.
Customer support service by UserEcho
If you go and look at the panel page you will find a list of object properties you can write to. Several attributes you are trying to change are not valid object properties.
What page were you at when you got the panel page missing link if you don't mind?