Yep, that's where the visible property is for. You could also override
isVisible instead of setting the property. Sometimes this is easier to
do if you're using some algoritm to see whether it should be displayed
(get see if you've got any elements in your list). The downside of
overriding however is that you lose backbutton support (though you could
manually re-introduce it again) for that property. Not such a big usually.
Eelco
Nick Heudecker wrote:
Thanks. I'll check it out after I finish playing golf. :) I have
another associated question.
If there aren't any Pricing objects for a given Track, I want to put a
message in the page like "You don't have pricing setup yet." The
problem is that if I put that span tag in the markup:
<span wicket:id="noPricingMessage">Test</span>
And don't add the object to the page, Wicket will throw an exception.
Will calling setVisible(false) get me around this?
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
