Well, in my use case, subcomponents use a Behavior#onConfigure() to change their own visibility, and this method is called after Component#onConfigure(), hence the visibility state is not uptodate.
Le 22 août 2016 13:54, "Sven Meier [via Apache Wicket]" < [email protected]> a écrit : > Why not override #onConfigure() and check the visibility of the child > components from there? > > Regards > Sven > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://apache-wicket.1842946.n4.nabble.com/Visibility- > Enability-change-event-tp4675352p4675353.html > To unsubscribe from Visibility/Enability change event, click here > <http://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4675352&code=Z3Vpb20ubWFyeUBnbWFpbC5jb218NDY3NTM1Mnw1NzIyNjk5Nzk=> > . > NAML > <http://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Visibility-Enability-change-event-tp4675352p4675360.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
