yes checking for enabled there is fine
(thats why wicket also does for setting the enabled attribute)
johan
On 10/27/07, nico <[EMAIL PROTECTED]> wrote:
>
> Johan Compagner schrieb:
> > why aren't you subclassing button and have a button that has that
> > modifier and use that one on all your f
Johan Compagner schrieb:
why aren't you subclassing button and have a button that has that
modifier and use that one on all your forms?
doh! thanks, i haven't seen that obvious possibility
..is it right, to check wether the button is enabled in the
onComponentTag event before putting the att
why aren't you subclassing button and have a button that has that
modifier and use that one on all your forms?
On 10/26/07, nico <[EMAIL PROTECTED]> wrote:
>
> Thanks, Johan
> > With that code you are adding an attribute modifier ever time the button
> renders
> > And you did get an exception i g
Thanks, Johan
With that code you are adding an attribute modifier ever time the button renders
And you did get an exception i guess because you call getString() out of the
blue inside a construtor of a not fully constructed class.
thats why i moved the code to the propably wrong place..
To
With that code you are adding an attribute modifier ever time the button
renders
And you did get an exception i guess because you call getString() out of the
blue inside a construtor of a not fully constructed class.
To do that you have to lazy get the string through a model.getObject().
Then als
Thanks, that worked for me,
however i needed to add the modifier in onBeforeRender, within the
constructor an exception
was thrown
@Override
public void onBeforeRender() {
submitButton.add(
new SimpleAttributeModifier("value",
me right now.
Jeremy Thomerson
-- sent from a wireless device
-Original Message-
From: "nico" <[EMAIL PROTECTED]>
To: users@wicket.apache.org
Sent: 10/24/07 3:52 PM
Subject: Re: i18n feedbackmessages
another issue,
Button.onComponentTag states in its documentation tag:
info(getString("your.key"));
Jeremy Thomerson
On 10/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hi, i wonder wether the
> info("feedback message"); could be internationalized, ie.
> info("feedback.success"); with a corresponding entry in the xyz.properties
> .
> is there a workaround?
info(getstring("feedback.success"));
-igor
On 10/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi, i wonder wether the
> info("feedback message"); could be internationalized, ie.
> info("feedback.success"); with a corresponding entry in the xyz.properties.
> is there a workaround?
> than
