There is the Wicket way of doing thing simple, and then there our own way of overriding the default behavior of the framework for whatever needs you might have.
In your case, I think you're overcomplicating things by way too much and you got yourself in a situation where it involved more work to accomplish something simple. Your code alone looks a bit too complicated to me for what is trying to do. I suggest you step back and list the use-cases you need and then approach the problem from a different angle. ~ Thank you, Paul Bors On Mon, Apr 29, 2013 at 10:47 AM, eugenebalt <eugeneb...@yahoo.com> wrote: > Thanks Sven, let me clarify something in your code: > > 1) #newItem only has the signature newItem(int); there is no > newItem(int,IModel). > 2) At the line "super.configure()" we get the error "The method configure() > is undefined for the type Check". > 3) When you make references to "enabled", I assume it's some global > flag/variable that you're checking, which is set outside in the main > module? > > Thanks > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Disabling-Individual-Checkboxes-in-CheckGroup-tp4658165p4658388.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 > >
