« Return to Thread: DatePicker not working after upgrading from 4.0.2 to 4.1

Re: DatePicker not working after upgrading from 4.0.2 to 4.1

by Roberto Ramírez Vique :: Rate this Message:

Reply to Author | View in Thread

Hi everybody!!!

I had the same problem as jani, and as he described I tried with the last
version of the jar files.... it seems to work, but the problem is the
location of the DatePicker, it appears just in a wrong place.

Is just not placed close to the icon, is just placed in the left-down part
of the page.

any of you have had the same problem ??? I'm using tomcat 5.5, jdk 5,
tapestry 4.1

Thanks in advance,
         robert

On 9/12/06, Robert Binna <r.binna@...> wrote:

>
> But be aware that you can't change the input dateformat at the moment,
> because the dojo DropdownDatePicker doesn't support it yet (but should
> from version 0.4 on)
>
> regards, Robert
>
> soir schrieb:
>
> >Hello,
> >
> >I've found same problem recently. Try to use DropdownDatePicker component
> >instead.
> >
> >Igor
> >
> >
> >Anders Cessner wrote:
> >
> >
> >>Hi,
> >>
> >>I recently upgraded from 4.0.2 to 4.1 and noticed that the datepicker
> >>doesnt
> >>work anymore.
> >>
> >>when the page is loaded i get this error: Could not load 'tapestry.form
> ';
> >>last tried '__package__.js'
> >>and when i click the calendar image i get: calendar_dueDate has no
> >>properties
> >>
> >>it has probably something to do with this
> >>http://issues.apache.org/jira/browse/TAPESTRY-1020?page=all as i´m
> >>developing on windows, but that issue seems to be resolved 21/7 and
> >>the 4.1jars i´ve downloaded from
> >>http://tapestry.apache.org/download.html looks like to be dated after
> >>that.
> >>
> >>what should i do to fix this?
> >>
> >>
> >>
> >>
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>


--
Robert Ramírez Vique
Computer Science Engineer

 « Return to Thread: DatePicker not working after upgrading from 4.0.2 to 4.1