D dilettante Active Member Licensed User Longtime User Dec 28, 2013 #1 DateTime.TimeZoneOffset returns a Double, pretty much as one would expect since there are "fractional" time zones. However DateTime.SetTimeZone() only accepts an Int value, which seems problematic. Is there a bug here or am I missing something?
DateTime.TimeZoneOffset returns a Double, pretty much as one would expect since there are "fractional" time zones. However DateTime.SetTimeZone() only accepts an Int value, which seems problematic. Is there a bug here or am I missing something?
Erel B4X founder Staff member Licensed User Longtime User Dec 29, 2013 #2 It will be changed to a Double in the next update.