To perform action in chronological order, you would want to use a sync tag. This would perform everything in a single action trigger though. Randomgroup will only perform one per trigger.

If you don't want your panels to overlap, consider putting them into a pager when you create them, that way they will fall in line.

Probably your best approach here is to onrotate based on orientation, delete the previous tableview and create the new one. Yes that means maintaining two tableview classes, but you can make each one look and feel the way you need it to.


<class name="pageItem">
<panel name="[param:name]" lwidth="512" lheight="768" width="1024" height="768" style="bgRed" valign="center">
<image name="pageImg" source="[param:imgSrc]" lwidth="512" lheight="768" width="768" height="1024"></image>
</panel>
</class>
<class name="table1">
<tableview name="mag" alias="MAG1" onclickup="showNav" width="100%" height="100%" rowheight="768" datasource="pagesFeed" orientation="horizontal" paginate="no">
<object datasource="pagesFeed" class="pageItem" name="page-[param:id]" imgSrc="[param:image]"></object>
</tableview>
</class>
<class name="table2"></class>
<tableview name="mag" alias="MAG2" onclickup="showNav" width="100%" height="100%" rowheight="1024" datasource="pagesFeed" orientation="horizontal" paginate="no">
<object datasource="pagesFeed" class="pageItem" name="page-[param:id]" imgSrc="[param:image]"></object>
</tableview>

<action name="create">
<if lhs="[system:orientation]" operator="e" rhs="landscape">
<create class="table2" target="..."/>
<delete target="MAG1"/>
</if>
<if lhs="[system:orientation]" operator="e" rhs="portrait">
<create class="table1" target="..."/>
<delete target="MAG2"/>
</if>
</action>



Greg,

WIRE can communicate with all sorts of external datasources. As long as the wifi controlled device is talking to a server and posting data, then WIRE can also communicate with the same data feeds and relay the information.

Richard,

In order for the widesource to work right now, you must assign an lwidth and lheight to the image that is using the widesource. I updated your code and it seems to work now.

Here is what it would look like:


<pager name="pager_name" width="100%" height="85%" lheight="83%" orientation="vertical" paginate="no" valign="bottom">
<panel name="button1" width="100%" height="40%">
<image name="pic1" source="beforeyouvisit_short.png" width="100%" lwidth="100%" lheight="100%" contain="no" widesource="beforeyouvisit_wide2.png"></image>
</panel>
<panel name="button2" width="100%" height="40%">
<image name="pic2" source="directory_short.png" width="100%" lwidth="100%" lheight="100%" widesource="directory_wide.png" contain="yes" clip="yes" align="left" valign="center" onclickup="show-directory"></image>
</panel>
</pager>


try giving your tableview a height.

your tableview is using an attribute called "pagination", that should read "paginate"

Without seeing the complete code, it is hard to say. Your list is defining a height that the tableview is not.

Is your tableview displaying a scroll or is it not appearing at all?

You could consider putting the alert in a sync block and setting a delay on it, this should help the issue. Though in an ad-hoc or release build you won't be seeing updates as frequently as in fusebox.

I have looked at the code and dug a little deeper and it does look like there is a bug. In order to get a widesource to work, noticed that I must use a lwidth and lheight to get the image to snap the new image into proper dimensions.

I have logged a bug report for this and it will go into our queue.

If you are viewing this in fusebox during a 'update content' then the alert could pop before and after the update. This should not happen otherwise.

Are you seeing this happen even without a content update?