wow check this out...
Ok at the bottom of my Gallery.TML
I have the actual beginning definition of my gallery code...
<!-- OK here is the definition. It is all referral declaration within <td>
-->
<table width="100%" border="3" align="center">
<tr>
<td>
<t:Any id="headerSelect">
<t:delegate to="autoPagingContent"/>
</t:Any>
<t:Any id="galleryContent">
<t:delegate to="collectionContent"/>
</t:Any>
<t:Any id="footerSelect">
<t:delegate to="autoPagingContent"/>
</t:Any>
</td>
</tr>
</table>
BTW: in T4... you cuold not exercise a duplicate reference to the same block...
as I am here in T5 for my auto-paging select's and eventlinks.
So I change it to this...
<!-- OK here is the definition. It is all referral declaration within <td>
-->
<table width="100%" border="3" align="center">
<tr>
<td>
<t:Any id="footerSelect">
<t:delegate to="autoPagingContent"/>
</t:Any>
</td>
</tr>
</table>
I removed headerSelect and pagingContent for shits and grins...
And it did impact the runtime...
1. the select components are keeping their selected value on selection instead
of snapping back to what they were initialized to.
2. the event links handlers are executing and modeling digitized event links in
between the prev/next event links like it should.
I am not sure what to say about this behavior but I am continuing to try and
shake this out.
I will admit... I did introduce a duplicate reference to a block... in order to
have auto-paging select/links/buttons at the top of the gallery and at the foot
of the gallery.
But I cannot explain all the memory issues.
I am still seeing nulls in the debugger though.
