Can you make this a new community topic please?

Unfortunately, the gallery and tile tags you are using are reserved only for images.

To accomplish what you desire, your second pager will have to contain a series of images or panels to represent a "play" button. On that play object you can put an onclickup attribute that will trigger a sound action tag.

<wire>


 <main> 


  <pager name="1" alias="TWO" width="100%" height="50%" orientation="horizontal" align="center" valign="bottom" paginate="yes" onscrollto="load2">


      <image name="1" source="play.png" onclickup="audioPlay" _sound="Music/05 Dice of Life"></image>


     <image name="2" source="play.png" onclickup="audioPlay" _sound="Music/Song2"></image>


     <image name="3" source="play.png" onclickup="audioPlay" _sound="Music/Song3"></image>


     <image name="4" source="play.png" onclickup="audioPlay" _sound="Music/Song4"></image>


   </pager>


 </main>


<actions>


  <action name="audioPlay">


    <set onclickup="audioStop" />


        <play anim="clip" _action="play" _source="_sound" _type="mp3" />


  </action>


  <action name="audioStop">


    <set onclickup="audioPlay" />


    <play anim="clip" _action="stop" _source="_sound" _type="mp3" />


  </action>


  <action name="clip">


    <sound action="_action" source="_source" type="_type"/>


  </action>


</actions>


</wire>

Your best bet here is to use conditional logic attributes on the object tag within your list.

We do this for feeds a lot.


<list name="twitter-list" alias="TWEET" width="100%" height="100%" datasource="twitter-feed" orientation="horizontal" paginate="no">
<object name="twitter" class="twitter-item" id="[param:dataSourceIndex]" tweet="[param:text]" lhs="[param:dataSourceIndex]" operator="lte" rhs="10"/>
</list>


This will cause the list to only render for the conditional statement listed, in this case it will display only the index numbers less than or equal to 10.

Currently we only support a one-to-one relationship with "onpage". Though this may be a good candidate for a feature request. I will submit a ticket!

Thanks!

Ah great I will check it out! Thanks.

It is important to suppress your images and use load actions. This will help manage your App memory.

This is probably happening because of an error in overlapping concepts in the WIRE. We are working hard on a debugging tool that will guide you to the issue. Look for that down the line.

Try using nested pagers, this should get you close to what you want to accomplish:

<wire>



    <main>


      <pager name="main" alias="MAIN" width="100%" height="100%" orientation="vertical" align="center" valign="center" paginate="yes">


        <pager name="2" alias="ONE" width="100%" height="50%" orientation="horizontal" align="center" valign="top" paginate="yes" onscrollto="load1">


          <image name="1" width="50%" height="50%" source="pic1.png" suppress="yes"></image>


          <image name="2" width="50%" height="50%" source="pic2.png" suppress="yes"></image>


          <image name="3" width="50%" height="50%" source="pic3.png" suppress="yes"></image>


        </pager>


        <pager name="1" alias="TWO" width="100%" height="50%" orientation="horizontal" align="center" valign="bottom" paginate="yes" onscrollto="load2">


          <image name="1" width="50%" height="50%" source="pic4.png" suppress="yes"></image>


          <image name="2" width="50%" height="50%" source="pic5.png" suppress="yes"></image>


          <image name="3" width="50%" height="50%" source="pic6.png" suppress="yes"></image>


        </pager>



      </pager>


    </main>


    <actions>  


      <action name="oninit" oninit="yes">


        <load  target="ONE" />


        <load  target="TWO" />


      </action>


      <action name="load2">


       <sync loop="no" startdelay="0">


         <load  target="TWO" />


         <unload  target="ONE" />


        </sync>


      </action>


       <action name="load1">


        <sync loop="no" startdelay="0">


         <load  target="ONE" />


         <unload  target="TWO" />


       </sync>


      </action>



     </actions>


</wire>

That is very strange! That is the main link and it should not take you to that odd link. You might try refreshing your cookies in your browser.

Were you able to get to it with the link I sent?