I've used the hiding trick as well, but in larger scaled applications this consumes too much memory (e.g. for tab-like components).
Eelco
Jonathan Locke wrote:
yeah, this was the other reason i didn't like setParent. it's just so useful sometimes.
one trick you can use sometimes is to /hide/ a component or panel or whatever. then the back button should work fine. it's just when you alter the components that wicket can't track things.
On Thu, 6 Jan 2005, Eelco Hillenius wrote:
And that respect... we might want to re-consider the replace method. Since I use replacing components (for tab-like behaviour), I have back button problems all of the time.
Eelco
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
