I’m not sure if it’s been fixed in the edge code, since the bug is
several
months old and is still open and I’m using 1.0. I also haven’t tried the
patches
in any of the bugs. I think I ended up using separate month and day
pulldowns
instead of a date_select(:discard_year => true).
I’ll use seperate pulldowns for now then and look out for when the
creases are ironed out.
Very much appreciate your help!
Doug
Hi Doug,
You might also want to check out the bundled_resource plugin I just
announced on the list, as it includes a novel way of entering 12-hour
time instead of 24-hour time.
While it’s not on the list of most-elegant solutions, it does the job
in a simple way: basically, the dynarch_calendar bundle re-opens the
DateTime class and allows the 6th parameter (normally seconds) to
optionally be an “AM” or “PM” string. If this is the case, it will
update the 1st parameter (the hour) to be a 24 hour parameter even
though only 12 hours are ever selectable by the user.
The dynarch_time_select method can be used independently, and does
not require any of the javascripts or stylesheets associated with the
dynarch calendar.
I’m not sure if it’s been fixed in the edge code, since the bug is
several
months old and is still open and I’m using 1.0. I also haven’t tried the
patches
in any of the bugs. I think I ended up using separate month and day
pulldowns
instead of a date_select(:discard_year => true).
Cheers,
stuart
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.