RE: [Wicket-user] Visibility of clearInput method

[Roan O'Sullivan]

Thanks for making the change Johan. Good to know about FormComponent#valid() 
method too. You guys are doing a great job of supporting your users.
 
Roan
 



From: [EMAIL PROTECTED] on behalf of Johan Compagner
Sent: Wed 5/10/2006 6:19 PM
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Visibility of clearInput method


you just want only to clear the input on that specific FormComponent?
So you don't want to call Form.clearInput() ?

Calling FormComponent.valid() does the same thing by the way. It clears the 
rawInput
(and calls onValid()) 

But i guess this is not that logical to do (know)
clearInput can be public final in my eyes.

johan



On 5/9/06, Roan O'Sullivan  [EMAIL PROTECTED] wrote: 

Could the FormComponent#clearInput() be made public? 
 
This is my scenario:
 
 * a recipient property on my model object
 * a DropDown (that listens to selection change events) lets users 
select from a list of Recipient beans
 * a TextField is bound to the email field for the model object's 
recipient property 
 
When I select a new Recipient, the display value of the email TextField 
is still blank. In 1.1.1 the TextField would show the new model object value 
(which is the correct behavior for my page). 
 
I assume the change in behavior with 1.2 is due to the introduction of 
FormComponent#rawInput (which, by the way, works like a dream in most other 
scenarios). The #getRawInput() method on the TextField bound to  
recipient.email returns empty string () in the #onSelectionChanged() 
listener for the DropDown bound to recipient.
 
If I could invoke #clearInput() on the TextField bound to 
recipient.email, I assume that model value for the newly selected recipient 
would get rendered just like I want it to. Are developers willing to consider 
API changes this late in the game for a 1.2 release?
 
If #clearInput() cannot (or should not) be made public, can anyone 
think of any other ways to achieve this effect?
 
Thanks, Roan


winmail.dat

Re: [Wicket-user] Visibility of clearInput method

[Johan Compagner]

you just want only to clear the input on that specific FormComponent?So you don't want to call Form.clearInput() ?Calling FormComponent.valid() does the same thing by the way. It clears the rawInput(and calls onValid())
But i guess this is not that logical to do (know)clearInput can be public final in my eyes.johanOn 5/9/06, Roan O'Sullivan 
[EMAIL PROTECTED] wrote:




Could the FormComponent#clearInput() be made public? 

This is my scenario:

* a recipient property on my model object
* a DropDown (that listens to selection change events) lets users select from a list of Recipient beans
* aTextField is bound to the email fieldfor the model object's recipient property 

When I select a new Recipient, the display value of the email TextField is still blank. In 1.1.1 the TextField would show the new model object value (which is the correct behavior for my page). 


I assume the change in behavior with 1.2 is due to the introduction of FormComponent#rawInput (which, by the way, works like a dream in most other scenarios). The #getRawInput() method on theTextField bound to 
recipient.email returns empty string () in the #onSelectionChanged() listener for the DropDown bound to recipient.

If I could invoke #clearInput() on the TextField bound to recipient.email, I assume that model value for the newly selected recipient would get rendered just like I want it to. Are developers willing to consider API changes this late in the game for a 
1.2 release?

If#clearInput()cannot (or should not) be made public, can anyone think of any other ways to achieve this effect?

Thanks, Roan

[Wicket-user] Visibility of clearInput method

[Roan O'Sullivan]

Could the FormComponent#clearInput() be made public? 

This is my scenario:

* a recipient property on my model object
* a DropDown (that listens to selection change events) lets users select from a list of Recipient beans
* aTextField is bound to the email fieldfor the model object's recipient property 

When I select a new Recipient, the display value of the email TextField is still blank. In 1.1.1 the TextField would show the new model object value (which is the correct behavior for my page). 

I assume the change in behavior with 1.2 is due to the introduction of FormComponent#rawInput (which, by the way, works like a dream in most other scenarios). The #getRawInput() method on theTextField bound to "recipient.email" returns empty string ("") in the #onSelectionChanged() listener for the DropDown bound to recipient.

If I could invoke #clearInput() on the TextField bound to "recipient.email", I assume that model value for the newly selected recipient would get rendered just like I want it to. Are developers willing to consider API changes this late in the game for a 1.2 release?

If#clearInput()cannot (or should not) be made public, can anyone think of any other ways to achieve this effect?

Thanks, Roan