Hello,
Using SmartGWT 3.0 Power.
I am building a little scheduling module in my app to schedule lectures.
When I use a datepicker to select a time beyond 25th of march, when Daylight Savings Time starts (Netherlands, which is GMT+1 or CET), and I pick say 10:00 am, upon blur the item corrects to 09:00am (a refocus and reblur will make it count down to 8am, 7am, etc.).
How can I prevent this correction, and completely ignore the matter?
The thing is, if I want to schedule a lecture at 09:00 am in June, I don't care what DST paradigm is being used, a teacher should just be able to see that he needs to be there at 9am.
So, I see how this feature can be useful, but for my particular case it is not.
Oh yes, I use a MySQL backend, where the particular field is of type DATETIME.
Any thoughts on how to deal with these things properly?
Using SmartGWT 3.0 Power.
I am building a little scheduling module in my app to schedule lectures.
When I use a datepicker to select a time beyond 25th of march, when Daylight Savings Time starts (Netherlands, which is GMT+1 or CET), and I pick say 10:00 am, upon blur the item corrects to 09:00am (a refocus and reblur will make it count down to 8am, 7am, etc.).
How can I prevent this correction, and completely ignore the matter?
The thing is, if I want to schedule a lecture at 09:00 am in June, I don't care what DST paradigm is being used, a teacher should just be able to see that he needs to be there at 9am.
So, I see how this feature can be useful, but for my particular case it is not.
Oh yes, I use a MySQL backend, where the particular field is of type DATETIME.
Any thoughts on how to deal with these things properly?
Comment