v1.0.9 - value="12:30" bug fix

Fix for #20

The issue was that if you set value="12:30" it would be interpreted as "12:30 AM" however it should have been interpreted as "12:30 PM".