Kishen Simbhoedatpanday wrote:
I thought the displayFormat was for display purposes only.
But "HH:mm" does not work when giving the currentTimePart "16:15".
It still gives the "00:00"
My only remaining suggestion is that you create a page full of time
pickers and try all the possible combinations. In our case we always
set the value attribute explicitly (separate from the name attribute)
and it has been working for the "h:mm a" pattern.
On a side note, we stopped using the time-picker anyway because the
client didn't like it - two simple selects with hours and mins in them,
backed by a javascript function to encode/decode the values into a
single time string was their preference and would have been less effort
to start with. Besides the trouble integrating the time-picker into
your application, the usability is questionable (popop->click hour->pops
down->popup again->click minute->popdown). The only thing it has going
for it is that is looks nice.
We still use the date-picker but will replace it jsCalendar or Musachy's
YUI plugin the next chance we get.
We also have the following issue...
When we change the currentTimePart to "16:35" and submit the form, the
currentTimePart value is: "2007-06-28T16:35:00+02:00".
Yeah, you'll have to parse it.
As I mentioned in a previous email, another option may be to use
javascript to concat the date component from the date picker with the
time component from a time picker, and post that value.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
