Timepicker 1.0.5, Selected

18 Responses

1. 

   Dmitry Chernyaev

   Oct 10, 2012

   Hi Trent!

   Thank you for your timepicker control. It is very useful for me.
   Unfortunately I have some problems setting minDate and maxDate in runtime.

   I have two textboxs: StartDate and EndDate.
   If I select some date with time in one control, date for other control becomes limited but time not.

   Here is code sample:
   

   $(function () {
var dates = $("#StartDate, #EndDate").datetimepicker({
dateFormat: 'dd/mm/yy',
timeFormat: 'hh:mm',
stepMinute: 15,
beforeShow: function(input, inst) {
var other = inst.id == "StartDate" ? "#EndDate" : "#StartDate";
var option = inst.id == "StartDate" ? "maxDate" : "minDate";
var selectedDate = $(other).datetimepicker('getDate');

   if (selectedDate !== null)
$(input).datetimepicker("option", option, selectedDate);
}
});
});

   Can you help with this?

2. 

   Paulo

   Oct 11, 2012

   Hello Trent,

   First, thanks for this plug-in, it’s a life saver.

   Second, thanks for the timezone fix (I got called on it today!).

   Now a problem I had:
   It’s most likely my project but I had to change in line 828
   “… return obj.prop(‘slide’, null).slider({ …”
   “… return obj.propAttr(‘slide’, null).slider({ …”
   or else it wouldn’t show the datetimepicker in my page.

   By the way I’m generating a timeZone list in my server code based on the
   server’s timezone list, and it has several timeZones with the same value,
   is there an easy away to select a default timeZone by the “label”?

3. 

   gokhan

   Oct 13, 2012

   Hi,
   How can I publish without

4. 

   gokhan

   Oct 13, 2012

   How can I publish without some pre

5. 

   Christopher Tilley

   Oct 16, 2012

   There is a bug which makes this addon completely unusable for me. It’s unfortunate because of the overall look and feel is outstanding. The issue is when you have ampm:true and you’re using altFormat and altTimeFormat, it will not convert correctly back to 24 hour time. for ex

   This:
   2012-10-16 03:15pm

   Is converted to this
   2012-10-16 03:15:00

   Instead of this:
   2012-10-16 15:15:00

   
$("#ship_display").datetimepicker
ampm: true
altField: "#shipment_ship_date"
altFormat: "yy-mm-dd"
altFieldTimeOnly: false
altTimeFormat: "hh:mm:00"


6. 

   trent

   Oct 19, 2012

   Hey Christopher, I don’t think this is a bug. You specified ampm: true, so it will be parsed as such, regardless of having ‘t’ within your timeFormat or not.

   That said though we need another option: altAmpm so that altFields may use a different ampm setting. I believe there is an open issue on Github for this, but have not gotten a chance to implement it.

7. 

   j.k

   Oct 19, 2012

   Hi trent and big thankyou for this sweet plugin!

   i have an issue with the new version 1.05(prev was 1.01) ,when i try the new one i get this error:

   return obj.prop(‘slide’, null).slider({
   — TypeError: obj.prop is not a function

   any idea why? i tried what Paulo said and it didnt helped..
   thanks

8. 

   trent

   Oct 20, 2012

   JK,
   Try upgrading jquery to at least 1.6, .prop was not available in earlier versions

9. 

   Neha Khanna

   Nov 21, 2012

   Thanks! You made my day.

10. 

    Neha Khanna

    Nov 21, 2012

    Thanks! You made my day.

11. 

    Boris

    Jan 03, 2013

    Hi,
    same problem for me:
    TypeError: obj.prop is not a function
    return obj.prop(‘slide’, null).slider({

    using jquery 1.8.2 & jqueryui 1.9.2 including it external through Google Hosted Libaries…
    any suggestions?

    Thx alot best regards
    Boris

12. 

    Adrian

    Apr 01, 2013

    Hi Boris,

    I was having the same trouble using Google libraries too and updating links to most current releases fixed the problem: Version 1.9.1 for the jquery and 1.10.2 for the jquery UI. https://developers.google.com/speed/libraries/devguide#jquery

    Best,
    Adrian

13. 

    poche

    May 24, 2013

    Hello,

    Thanks a lot for this really nice plugin.

    I have a little problem, I’m using it for a drupal website, but when I click on the textfield which should display the values to select from, those values appears at the very end of the webpage (instead of being attached to the textfield)

    This is due to the fact that the plugin adds the div:

    Just before the closing … shouldn’t it be inserted in the same div as the textfield?!

    Thanks a lot,
    poche

14. 

    poche

    May 24, 2013

    Sorry but my html code was censured by your website :)

    Here is the div
    div class=”ui-timepicker-wrapper” tabindex=”-1″ style=”position: absolute; left: 847.367px; display: block;”

    Which is put by the plugin just before the closing body tag instead as the same div as the textfield.

    Thanks,div class=”ui-timepicker-wrapper” tabindex=”-1″ style=”position: absolute; left: 847.367px; display: block;”
    poche

15. 

    trent

    May 28, 2013

    Hey poche, Timepicker is simply inserted inside of datepicker. I think if it is an inline datepicker it will be inserted in the div, otherwise there is just one at the end of the body that gets absolute positioned to which ever input has focus. This is a jQueryUI datepicker thing, not necessarily a timepicker thing.

    I would run a validation check on the html, sounds like there may be some broken tag somewhere..

16. 

    sergey

    Jun 05, 2013

    problem with error
    TypeError: obj.prop is not a function
    return obj.prop(‘slide’, null).slider({
    on jquerry 1.3.2
    solved by change obj.prop to obj.attr

17. 

    Vikas

    Jun 06, 2013

    Hi Trent,

    I’m stuck in a issue where i’ve to add two custom buttons on the calendar like “Today” button, so i’ve
    added those two buttons on “beforeShow” Event, now the issue is that whenever i click on those buttons or select any date or change Month.., those butttons are getting removed from the calendar.
    And i tried them adding again on other events like “onSelect”, “onMonthChange” etc., but it is clearly seen that buttons are getting removed and are being generated again.
    Can u please suggest.

18. 

    Scott

    Jun 07, 2013

    sergey’s comment worked for me on 1.71. Thanks, Trent – great plugin.