Sven,
That method was new to me :)
Everyday a new thing to learn. That's great.
And it works. Thanks :)
Eyal
On Tue, May 27, 2008 at 8:31 PM, Sven Meier [EMAIL PROTECTED] wrote:
Hello Eyal,
you did override #localizeDisplayValues() to return true, didn't you?
Sven
Eyal Golan schrieb:
Hello Eyal,
you did override #localizeDisplayValues() to return true, didn't you?
Sven
Eyal Golan schrieb:
I can but I thought there might be a way with the properties file.
Like the one with the null value.
Eyal
On Tue, May 27, 2008 at 11:15 AM, Martin Makundi
[EMAIL PROTECTED] wrote:
Hi!
Does the Wicket localizer support overriding localization for each
component? This is what I have:
add(new DropDownChoice(TYPE_PICKER, typeChoices));
add(new DropDownChoice(DATE_PICKER, dateChoices));
I would like to localize the null choice differently. Now it reads
Choose one for both
In the properties file for your page do:
component1Id.nullValid=Choose type
component2Id.nullValid=Choose date
Instead of just the id you can also include the (partial) path,
working your way to the top from the component you are trying to use.
Maurice
On Wed, May 21, 2008 at 8:08 PM, Martin
Duh, that was easy. Actually what I was looking for is
component1Id.null=Choose type
component2Id.null=Choose date
but thank you very much!
2008/5/21 Maurice Marrink [EMAIL PROTECTED]:
In the properties file for your page do:
component1Id.nullValid=Choose type
component2Id.nullValid=Choose
