Hi Paul, Thanks for your suggestion, hadn't tried that, but I have now and it doesn't fix my problem.
I use the idiom rather than simply calling Because: 1. depending on the situation it can lead to many setVisible calls in different parts of the page 2. it localises the visible setting to the component to which it applies 3. i don't need to pepper the code with lots of references to the component whose visibility is to be set 4. http://wicketinaction.com/2011/11/implement-wicket-component-visibility-changes-properly/ Thanks anyway for your suggestion, Cheers Simon -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/form-processing-adding-new-inputs-with-an-ajax-onupdate-tp4658758p4658778.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
