It's worth noting that if your grid is in a component then activation context
might not be suitable. A solution is on the way:
https://issues.apache.org/jira/browse/TAP5-2297
Cheers,
Geoff
On 27 Aug 2014, at 11:08 am, Chris Mylonas <ch...@opencsta.org> wrote:
> Hi Tapestry Noobs of the future!
>
> ...that come across this problem,use onPassivate to keep your app working
> nicely.
>
> I had the pleasure of using my software in a field trial (nothing exciting,
> equipment tracking in a data centre) and made a few adjustments to quicken
> my task though the night although forgot about onPassivate.
>
> So where I dev'd for 15 hours for a functional field test, I gave myself a
> usability conundrum for a few hours in the weeeee-small hours by not being
> able to sort within a context. (The irony is I was too proud to hook up
> the Internet to save wifi on my laptop - data centre is full of both
> internet and power!) - So the last half a dozen cables I couldn't
> trace....well there's room for another field trial!
>
>
> void onActivate(Long id) { store it here....use to get your data in
> setupRender() };
> Long onPassivate() { return your-passed-in-parameter-usually-Long };
>
>
> Happy deving!
> Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
