Your comments
This snippet might help.
<wire>
<main>
<panel name="list-container" alias="HIGH" width="100%" height="100%">
<panel name="yes" alias="YES" width="100" height="100" align="center" valign="center" onclickup="grow" background="ff0000">
<web name="hi" alias="HI" width="100%" height="100%" align="center" url="about://blank" pagetofit="yes" alpha="0"></web>
</panel>
</panel>
</main>
<actions>
<action name="grow">
<sync loop="no" startdelay="0">
<scale time="1" width="100%" height="100%" align="center" valign="center" target="YES" />
<load url="http://espn.com" target="HI" />
<alpha value="1" time="0" target="HI" />
</sync>
</action>
</actions>
</wire>
If you have the image set to dimensions smaller than it actually is (limiting it by making it a child of a smaller panel for example) and then invoke zoomable, you should be able to pinch out to make it "actual size".
When zoomable is set, the object will pinch zoom within its bounds. Zoomable can’t live at the root, you must assign at least one parent to base the zoom on.
Value = yes/no
When zoomable is set, the object will pinch zoom within its bounds. Zoomable can’t live at the root, you must assign at least one parent to base the zoom on.
Value = yes/no
onhover allows for you to trigger an action when you drag another object over an object or drag your finger from a down state somewhere else over the object.
Have you tried to applying the attribute called "pagetofit=yes" on your web tag? This should display it based on the size of the container.
If you check out the documentation on the panel tag, it will give you a general idea of action triggering gestures such a onswipe and onrotate.
right now most pinching is supported with the attribute called zoomable that is an extension of the panel.
We currently do not have a list dedicated to gestures, but I will take this request under consideration.
right now most pinching is supported with the attribute called zoomable that is an extension of the panel.
We currently do not have a list dedicated to gestures, but I will take this request under consideration.
One of the great things about the WIRE language is that it is constantly being upgraded and added to. Object Variables are an older concept that in its infancy was a great way to communicate with the action tag you were using on your object.
Now that the WIRE is a little older we have more advanced concepts of variables and parameters you can use, yet our legacy code is still available for use. In other words there is more than one way to skin a cat.
I understand what you are saying in your example, however it seems that if you plan to use object variables in your object that you would need to be more aware of the usage in the action it calls. Since it functions only at one level and serves to replace a value anyway, we feel that is a manageable request.
Now that the WIRE is a little older we have more advanced concepts of variables and parameters you can use, yet our legacy code is still available for use. In other words there is more than one way to skin a cat.
I understand what you are saying in your example, however it seems that if you plan to use object variables in your object that you would need to be more aware of the usage in the action it calls. Since it functions only at one level and serves to replace a value anyway, we feel that is a manageable request.
I think you are approaching these the wrong way. You utilized it correctly, it was simply an underscore that the variable didn't like.
An object variable allows you to define an arbitrary attribute whose value can then be used to identify a single object. When you use an object variable you can only pass the value to an action on one level, this is different than a [var:] that can be reused in several locations once defined.
In an assign capacity, you can only use an object variable as a one to one from the object that triggers the assign to the assign. And in your case you are assigning a wire variable the value of an object variable. The difference is that a wire variable is stored on the App for the entire session, the App only remembers an object variable getting passed from the object to an action one time.
What you are suggesting above would only be useful if you were using a class to define an object tag. This could be done like this: _myvar="[param:myvar]" This creates a parameter for the object variable you want to use.
A parameter's purpose is to capture an attribute's value for reuse within the WIRE. This allows the same class or object to be used many times with different content.
An object variable allows you to define an arbitrary attribute whose value can then be used to identify a single object. When you use an object variable you can only pass the value to an action on one level, this is different than a [var:] that can be reused in several locations once defined.
In an assign capacity, you can only use an object variable as a one to one from the object that triggers the assign to the assign. And in your case you are assigning a wire variable the value of an object variable. The difference is that a wire variable is stored on the App for the entire session, the App only remembers an object variable getting passed from the object to an action one time.
What you are suggesting above would only be useful if you were using a class to define an object tag. This could be done like this: _myvar="[param:myvar]" This creates a parameter for the object variable you want to use.
A parameter's purpose is to capture an attribute's value for reuse within the WIRE. This allows the same class or object to be used many times with different content.
It looks like what is preventing this from working is the underscore you have on your var:curr_myvar. It doesn't like the underscore, when I remove it, it works just fine. I will show this to the dev team.
Object variables only work when defined as an object attribute on an object tag. In your example, you are attempting to define the object variable on an action. This is what is causing your issue.
Customer support service by UserEcho
https://vimeo.com/38846256