well there's something i didn't even think of...
On Sat, Apr 16, 2016 at 5:07 PM, Roger Eller
wrote:
> Local Time is the only one that is not selectable, and should also be the
> default. I have already filed a bug for that, and it has been confirmed.
>
> ~Roger
>
Local Time is the only one that is not selectable, and should also be the
default. I have already filed a bug for that, and it has been confirmed.
~Roger
On Apr 16, 2016 12:25 PM, "Mike Kerner" wrote:
> I think that depends on how you have the tz db set up. The
I think that depends on how you have the tz db set up. The other, simpler
option, I suppose, is to pull the local time from the host machine
On Fri, Apr 15, 2016 at 4:33 PM, Peter TB Brett
wrote:
> On 15/04/2016 21:29, Mike Kerner wrote:
>
>> I thought I already
On 15/04/2016 21:29, Mike Kerner wrote:
I thought I already reported this when I reported the time zone problem,
but maybe I forgot DST.
Oh, cool. I think they're actually different manifestations of the same
problem, so when one is addressed the other should be too.
I thought I already reported this when I reported the time zone problem,
but maybe I forgot DST.
On Fri, Apr 15, 2016 at 12:51 PM, Peter TB Brett
wrote:
> On 15/04/2016 17:42, John Dixon wrote:
>
>> put a clock widget on a card... set the time to your time zone...
>>
On 15/04/2016 17:42, John Dixon wrote:
put a clock widget on a card... set the time to your time zone...
In both the IDE and the simulator, everything is good in that it shows the
'correct' time...
Load it onto a dvice and the clock is an hour behind, I guess it knows nothing
about daylight
put a clock widget on a card... set the time to your time zone...
In both the IDE and the simulator, everything is good in that it shows the
'correct' time...
Load it onto a dvice and the clock is an hour behind, I guess it knows nothing
about daylight saving...:-(
Others seeing this ?