You should have no problems testing this in fusebox as long as the ad tag is implemented in the right places.

Steve,

PUT is currently not supported on our httpheader. We have this on our roadmap and it will be available soon.

You should be able to use POST in the meantime to accomplish what you need.

Richard,

That is good to hear. I was talking with the Dev team yesterday and in an upcoming release we will offer a solution to this problem. An enhancement that can dispatch events to pager/list/tableviews during the scroll, instead of waiting for the scrolling to stop. So that should be a nice addition to the WIRE language.

The issue lies with the children of an object with a clickdelay on it. If you select a child object, then it triggers the action immediately. If you select outside of the child, then it works.

In your first panel, your text child was set to 100%x100% so there was nowhere you could click that wouldn't trigger the action.

As a workaround, If you set the children to ignoretouches="yes" then it works as designed.

I will log a bug report for this. Thanks!

Steve,

clickdelay is an interesting tag. Here are a few details surrounding it.

1) clickdelay is only valid on the attribute "onclick"

2) the clickdelay value is counted when the object has a downstate active. In other words as long as your finger is touching the object the clickdelay will count.

3) The corresponding action will not fire until an upstate is detected AND the clickdelay time is satisfied.

So in your case, you could have an action like this:

<!--insert actions that will update the screen content-->

url is not a valid object property, so you would not be seeing that alert the way you have created it.

As far as the 404, I don't see how that would be a wire issue. Must have been a weird spot on your server.

Tyler,

paginate was created to only display one "page" or item in the pager at a time, so paginate is not going to get you the desired effect that you want in this case.

One option you could take is to place "filler" items inside of the pager to space your actual panels out to where you want them. This way you could use paginate="no" and still get the spacing correct. You would lose the snapping effect though.

Currently there are only two android platform tags. We will add more soon.

You can use: androidtablet and/or androidphone.

Unfortunately there is nothing you can do about this. This is the way scrolling actions must work (both scrollto and scrollaway). You can only guarantee that an action is fired when the user stops as you have described.

This is happening because you are assigning the datasource and the alert oninit. The system is trying to kick off both actions at the same time. Usually if you are assigning a datasource oninit you might as well just put the source in your datasource tag.

If you want to keep it like this, try putting the assign and alert in a sync block, so they will run in order.