Before committing to a - as you said wierd requirement - by breaking the form structure, I'd rather do the setEnabled() - dance but separate it into a special behavior attached to the form. So you have your requirement fulfilled while keeping the GUI code clean and readable.
-- View this message in context: http://apache-wicket.1842946.n4.nabble.com/One-field-enabled-in-a-disabled-container-tp4665156p4665158.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
