Subrata,

In the meantime, you can download our app Spark to access documentation information as well. You can find it in Android and iOS: 

https://itunes.apple.com/us/app/rarewire-spark/id6...
https://play.google.com/store/apps/details?id=com.rarewire.spark

Subrata,

We are aware of the incorrect link path for the documentation site. This should be correctly shortly. 

I am sure there are probably other solutions, but this seems to do what you want. 

Image here: http://i.imgur.com/l2fSum8.jpg

Try out this WIRE:

---

<wire>
    <main>
    <pager name="main" width="200%" height="100%" orientation="horizontal" paginate="no">
      <image name="img" height="100%" source="big.jpg" zoomable="yes" zoomscale="5" zoomcenter="yes" draggable="yes" dragorientation="horizontal"></image> 
      <panel name="fill" width="40%" height="100%"></panel>
    </pager>  
    </main>
  </wire>

Subrata, 

You can always access our documentation site from the main App Creation Studio. The link called "Developer Resources" in the top navigation bar will take you there. Additionally there is a link inside of our WIRE editor under "Help > Documentation.

Otherwise you can access it here: RareWire Documentation

Download Spark iOS: https://itunes.apple.com/us/app/rarewire-spark/id6...
Download Spark Android:  https://play.google.com/store/apps/details?id=com.rarewire.spark

If you have downloaded fusebox, then you will be able to log in with your studio account and see your app listed. Clicking on it will allow you to view your functioning app inside of fusebox. 

Check out this tutorial: https://studio.rarewire.com/wordpress/2012/02/using-fusebox-tutorial/

It is currently still working as described above, however you do have the option to change your binary version when you publish for the first time. It still defaults in our studio as 2.3, but if you have never made a build before, you can change it to 1.0 and it will then auto-increment based on that number moving forward. 

Unfortunately, if you make even a single build as 2.3, then you must always build higher than that out of the studio, so if you want to change it, you need to move to 2.4 or higher. The system will still assign a third number automatically. 

Now all that being said, the display version that users in the iTunes store see does not have to match this number. When you submit to the store you will see an alert to notify you that they don't match, but it is not required. 

So bottom line is that if you did not move to 1.0 on your first build then your binary version and display versions will not match unless your make your display version 2.3 or higher. Though, the end user should never see your binary version. 

Can you go ahead and email me your app id so I can take a look at what you have so far. (community@rarewire.com)

Yes. You would still use an onclickup to launch the details modal, but also a scroll action to move the secondary pager (list) to the correct spot. 

I visualize it as leaving a single panel up and scrolling through new data "cards". Rather than closing a panel and reopening a new one every time. Unless of course the user closes it and scrolls through the name list and selects a new name to launch details for. 

If you want to make your secondary detail panel a list that has paginate enabled, wouldn't that achieve the effect you are looking for?

Then you can use the action that launches the secondary panel to scroll to the item page that one selects from the list and it will then be swipeable left and right to the rest of the data set. 

You could even add arrow icons that can scroll next and back to get it the illusion that it is not a scrolling list. 

I assume you are referring to this section:

<panel name="icon" alias="ICONSELECT" xpos="2%" ypos="40%" height="12%" width="96%" >

<image name="sun" alias="SUN" source="sun.png" _source="" align="left" contain="yes" onclickup="addsun" /> 

<image name="tooth" alias="TOOTH" source="tooth.png" _source="" rightof="SUN" contain="yes" onclickup="addtooth"/>

<image name="dishes" alias="DISHES" source="dishes.png" _source="" rightof="TOOTH" contain="yes" onclickup="adddishes"/>

<image name="bed" alias="BED" source="bedroom.png" _source="" rightof="DISHES" contain="yes" onclickup="addbed" />

</panel>

Because your parent panel is in percentages, you can't reasonably rely on android to not stretch depending on the device. You will need to define height and width to the images in pixels in order to make sure that they stay static.