Re: DatePicker NaN
Verified fixed in 1.3.1. -- View this message in context: http://www.nabble.com/DatePicker-NaN-tp12759906p15446234.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DatePicker NaN
On Thu, 3 Jan 2008 21:29:18 +0100 "Gerolf Seitz" <[EMAIL PROTECTED]> wrote: > Federico, is it possibly that you try it with the latest trunk? > the fix is in and it will be included in 1.3.1 I'll try it ASAP, many thanks! :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DatePicker NaN
Federico, is it possibly that you try it with the latest trunk? the fix is in and it will be included in 1.3.1 Regards, Gerolf On Jan 3, 2008 10:58 AM, Federico Fanton <[EMAIL PROTECTED]> wrote: > On Wed, 19 Sep 2007 18:19:15 +0200 > "Gerolf Seitz" <[EMAIL PROTECTED]> wrote: > > > ivana filed an issue today (WICKET-989) and i already attached a patch > to > > it. > > so either you persuade any of the committers to apply the patch and > commit > > it, or you do an svn checkout and apply the patch to your local copy of > > wicket-datetime. > > > > Gerolf > > > > On 9/19/07, Philip Köster <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > ivana wrote: > > > > > > > > Hi > > > > I have a problem with the DatePicker. It works fine if the input is > a > > > > valid date or if the input is very wrong, for example: ''xxx". > > > > But when the input consists of numbers and but is not a valid date, > the > > > > calendar is rendered with NaN in every field. > > > > I'm sorry, could it be that somehow this patch wasn't included in 1.3.0? I > upgraded today and I'm still having the same problem.. If I write "123" in > the text box and I press the calendar icon, the datepicker is full of NaNs. > I checked wicket-date.js and it looks like it doesn't check for NaNs.. > Thanks for your time! > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: DatePicker NaN
i reopened the issue and will take a look at it tonight. thanks for reporting it. Gerolf On Jan 3, 2008 10:58 AM, Federico Fanton <[EMAIL PROTECTED]> wrote: > On Wed, 19 Sep 2007 18:19:15 +0200 > "Gerolf Seitz" <[EMAIL PROTECTED]> wrote: > > > ivana filed an issue today (WICKET-989) and i already attached a patch > to > > it. > > so either you persuade any of the committers to apply the patch and > commit > > it, or you do an svn checkout and apply the patch to your local copy of > > wicket-datetime. > > > > Gerolf > > > > On 9/19/07, Philip Köster <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > ivana wrote: > > > > > > > > Hi > > > > I have a problem with the DatePicker. It works fine if the input is > a > > > > valid date or if the input is very wrong, for example: ''xxx". > > > > But when the input consists of numbers and but is not a valid date, > the > > > > calendar is rendered with NaN in every field. > > > > I'm sorry, could it be that somehow this patch wasn't included in 1.3.0? I > upgraded today and I'm still having the same problem.. If I write "123" in > the text box and I press the calendar icon, the datepicker is full of NaNs. > I checked wicket-date.js and it looks like it doesn't check for NaNs.. > Thanks for your time! > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: DatePicker NaN
One way I work around this problem is to put the following on the textfield for the date picker: onfocus="this.blur();" Doing that means the user can't simply type in the date, but you don't have the NaN problem either. On Jan 3, 2008 3:58 AM, Federico Fanton <[EMAIL PROTECTED]> wrote: > On Wed, 19 Sep 2007 18:19:15 +0200 > "Gerolf Seitz" <[EMAIL PROTECTED]> wrote: > > > ivana filed an issue today (WICKET-989) and i already attached a patch > to > > it. > > so either you persuade any of the committers to apply the patch and > commit > > it, or you do an svn checkout and apply the patch to your local copy of > > wicket-datetime. > > > > Gerolf > > > > On 9/19/07, Philip Köster <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > ivana wrote: > > > > > > > > Hi > > > > I have a problem with the DatePicker. It works fine if the input is > a > > > > valid date or if the input is very wrong, for example: ''xxx". > > > > But when the input consists of numbers and but is not a valid date, > the > > > > calendar is rendered with NaN in every field. > > > > I'm sorry, could it be that somehow this patch wasn't included in 1.3.0? I > upgraded today and I'm still having the same problem.. If I write "123" in > the text box and I press the calendar icon, the datepicker is full of NaNs. > I checked wicket-date.js and it looks like it doesn't check for NaNs.. > Thanks for your time! > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Nick Heudecker Professional Wicket Training & Consulting http://www.systemmobile.com Eventful - Intelligent Event Management http://www.eventfulhq.com
Re: DatePicker NaN
On Wed, 19 Sep 2007 18:19:15 +0200 "Gerolf Seitz" <[EMAIL PROTECTED]> wrote: > ivana filed an issue today (WICKET-989) and i already attached a patch to > it. > so either you persuade any of the committers to apply the patch and commit > it, or you do an svn checkout and apply the patch to your local copy of > wicket-datetime. > > Gerolf > > On 9/19/07, Philip Köster <[EMAIL PROTECTED]> wrote: > > > > > > > > ivana wrote: > > > > > > Hi > > > I have a problem with the DatePicker. It works fine if the input is a > > > valid date or if the input is very wrong, for example: ''xxx". > > > But when the input consists of numbers and but is not a valid date, the > > > calendar is rendered with NaN in every field. I'm sorry, could it be that somehow this patch wasn't included in 1.3.0? I upgraded today and I'm still having the same problem.. If I write "123" in the text box and I press the calendar icon, the datepicker is full of NaNs. I checked wicket-date.js and it looks like it doesn't check for NaNs.. Thanks for your time! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DatePicker NaN
ivana filed an issue today (WICKET-989) and i already attached a patch to it. so either you persuade any of the committers to apply the patch and commit it, or you do an svn checkout and apply the patch to your local copy of wicket-datetime. Gerolf On 9/19/07, Philip Köster <[EMAIL PROTECTED]> wrote: > > > > ivana wrote: > > > > Hi > > I have a problem with the DatePicker. It works fine if the input is a > > valid date or if the input is very wrong, for example: ''xxx". > > But when the input consists of numbers and but is not a valid date, the > > calendar is rendered with NaN in every field. > > I ran into the exact same problem today. Is there any work-around for > this? > Is there anything I can do from the Java side to get a hook when parsing > the > input fails? > > Best > Philip > -- > View this message in context: > http://www.nabble.com/DatePicker-NaN-tf4475178.html#a12780712 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: DatePicker NaN
ivana wrote: > > Hi > I have a problem with the DatePicker. It works fine if the input is a > valid date or if the input is very wrong, for example: ''xxx". > But when the input consists of numbers and but is not a valid date, the > calendar is rendered with NaN in every field. I ran into the exact same problem today. Is there any work-around for this? Is there anything I can do from the Java side to get a hook when parsing the input fails? Best Philip -- View this message in context: http://www.nabble.com/DatePicker-NaN-tf4475178.html#a12780712 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DatePicker NaN
> another question eelco: what is the hidden input right after the > .yui-container span for? > iirc, it doesn't even have a name or id. see DatePicker#onRendered. Don't remember that, and looking at it, it doesn't really make sense. If you remove it and it still works, I'm fine with getting rid of it. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DatePicker NaN
Eelco Hillenius wrote: On 9/18/07, Gerolf Seitz <[EMAIL PROTECTED]> wrote: no, it's not intentional. could you please file a bug report? Yes please. What do we want here? The date picker not showing up in the first place? i'd say: have the datepicker clear the incorrect data from the form field -- Wouter Huijnink Func. Internet Integration W http://www.func.nl T +31 20 423 F +31 20 4223500 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DatePicker NaN
On 9/18/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > Yes please. What do we want here? The date picker not showing up in > the first place? hm, maybe use the previously correct date? another question eelco: what is the hidden input right after the .yui-container span for? iirc, it doesn't even have a name or id. see DatePicker#onRendered. gerolf - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: DatePicker NaN
On 9/18/07, Gerolf Seitz <[EMAIL PROTECTED]> wrote: > no, it's not intentional. > could you please file a bug report? Yes please. What do we want here? The date picker not showing up in the first place? Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DatePicker NaN
no, it's not intentional. could you please file a bug report? thanks... gerolf On 9/18/07, Ivana Cace <[EMAIL PROTECTED]> wrote: > > Hi > I have a problem with the DatePicker. It works fine if the input is a > valid date or if the input is very wrong, for example: ''xxx". > But when the input consists of numbers and but is not a valid date, the > calendar is rendered with NaN in every field. > I'm guessing this is a bug somewhere in the JS, or is it intentional? > > > > > > > -- > Ivana Cace > Func. Internet Integration > W http://www.func.nl > T +31 20 423 > F +31 20 4223500 > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
