consistancy of output -- input

[Petersdavis]

Hello,

Thank you for providing this excellent tool. One area of inconsistency is with the 12 hour clock. If I take a val() and store it to my database.. When I initialize a new wicked picker with the same value it returns NAN error. You could fix it pretty easily with regexpressions getting [\d]{1,2}[:][\d]{2} -- for the time [A][M] [P][M] --adding 12hrs if it is PM.

[lsascha]

That is also one thing i currently have an issue with. In the framework i use i can configure the datetime format, but that is then used for input AND output. Like it is now, it can't read the correct time again since input and output format are inconsistent with this script. :/

Other then that this script would have looked really nice. Will see if i can workaround it or if i need to use a different timepicker...

[Frank004]

Any solution on this. On my App, it overwrites the database value outputs on the field and presents the current time from the script. I'm saving it as string

[Petersdavis]

You can work around easily by sanitizing data before initializing the timepicker--or by sanitizing the data that you read from the timepicker. I was suggesting that expected behavior of the timepicker would be to accept its own outputs as inputs without manually sanitizing them.