Count up invalid result in HOURS section

[wimbarelds]

Count up invalid result in HOURS section

[chukwu]

Just like every coder, you must be very busy doing your own thing at work which somehow serves a better 'purpose'. I recommend you create a quiet weekend to fix the few setbacks on your plugin.Stabilize it. It is obviously attracting a lot of intention which is a good. thanks mate.

[wimbarelds]

I'm not sure why you closed this, I haven't had time to deal with this (since I've had much more important things to deal with in the past week), and I could not easily reproduce this.

Is this no longer a problem somehow? If it's still a problem, no reason to close it.

[chukwu]

Well, I closed it because it was quite a logical issue that erupts on intervals. Sometimes, it works as expected. Other times it acts crazy. I generate my data-date attribute dynamically using c#. I think the problem is AM/PM time format. It would be better if the time format is 24hours rather than the the 12hours AM/PM e.g 13:00:00. With C#, i had to change the culture info to yyyy-MM-dd HH:mm:ss rather than the yyyy-mm-dd hh:mm:ss cultureinfo. This change did not work two days ago but worked today. I dont get it. Thats why i closed it. It could be a logical bug or not.

[wimbarelds]

If you could provide example HTML/JavaScript that has this problem, that will help a lot. Note though, the recommended datetime format is 24h based (not am/pm)

[chukwu]

The example is very basic but the data-date html attribute is dynamically generated from the server and rendered using ajax load. The rendered result is plain html. e.g

The above code produced an incorrect result of 12hours which made me assume the plugin was reading my datetime as a AM time. when i inspected the DOM in chrome. The datetime rendered server side was 2014-01-12 04:33:39. It worked yesterday after changing my datetime format server-side to:

Your documentation stated datetime to be yyyy-mm-dd hh:mm:ss meanwhile what worked for me was yyyy-MM-dd HH:mm:ss. The examples on your documentation for dynamic time uses AM/PM input type. I suppose it raises confusion. I believe this may not be a BUG but an unclear documentation.

$('.deadline_tick').not('.escape_mepls').each(function () {
$(this).show(1000, function () {
$(this).TimeCircles().addClass('escape_mepls');
});
});

[chukwu]

I'm having problem attaching html code on github. NO EDITOR?

[wimbarelds]

The "reason" the example has an AM/PM input, is because it's a default HTML5 time input field. It's not by choice or something alike.

[wimbarelds]

I think this is no longer an issue and was actually only an issue with input, correct? I have changed the demo page to avoid this misunderstanding (as well as making that page much more awesome). If this is still a problem, please let me know.