> On Mar 18, 2016, at 8:53 AM, Bert Freudenberg <bert at freudenbergs.de> wrote:
> 
>> On 18.03.2016, at 16:46, Eliot Miranda <eliot.miranda at gmail.com> wrote:
>> 
>>> On Mar 18, 2016, at 8:32 AM, Bert Freudenberg <bert at freudenbergs.de> wrote:
>>> 
>>> Or even better: setting the timezone should modify local time, not UTC. I guess that’s one of the motivations for Dave’s re-implementation.
>> 
>> ?!?! UTC should /never/ be changeable.  One can alter one's conputer's clock to simulate computing in a different age, but UTC is supposed to be UTC and is entirely independent of time zone.
> 
> Agreed. But right now DateAndTime still stores local time:
> 
> | a b |
> DateAndTime automaticTimezone: true.
> a := DateAndTime now asUTC.
> DateAndTime automaticTimezone: false.
> DateAndTime localOffset: 5 hours.
> b := DateAndTime now asUTC.
> {a. b}
> ==> {2016-03-18T15:50:21.731797+00:00 . 2016-03-18T11:50:21.731797001+00:00}
> 
> Which makes no sense. We should fix that, and I’m pretty sure it is fixed in David’s version. 

Phew :-)

> 
>>> If that were the case, then the clock in the tool bar would reflect the time in a different time zone, and people would eventually notice. No need for a warning. Hmm, I like that!
>> 
>> And indeed the title bar clock could include the time zone abbreviation.
> 
> We don’t know the abbrev … but showing the “wrong” time should be good enough.

I really should add a getenv: prim.  Absurd that one has to load OSProcess (or use NativeBoost) just to get at environment variables.

> 
> - Bert -
> 
>>> - Bert -
>>> 
>>>> On 18.03.2016, at 16:12, Bert Freudenberg <bert at freudenbergs.de> wrote:
>>>> 
>>>> There is a preference for that (DateAndTime automaticTimezone: false). 
>>>> 
>>>> Interesting idea to automatically disable the pref when setting the timezone manually … Although I’m not sure that should happen silently. Maybe a warning should pop up telling you that you probably want to disable the pref?
>>>> 
>>>> - Bert -
>>>> 
>>>>> On 18.03.2016, at 15:26, Max Leske <maxleske at gmail.com> wrote:
>>>>> 
>>>>> I found the problem. DateAndTime gained “automatic timezone”. So when I change the timezone in my tests it doesn’t have an effect unless I disable that.
>>>>> 
>>>>> You should think about disabling automatic timezone when the timezone has been changed manually. When I change the timezone I expect that change to be effective.
>>>>> 
>>>>> Cheers,
>>>>> Max
>>>>> 
>>>>> 
>>>>>> On 16 Mar 2016, at 08:21, Max Leske <maxleske at gmail.com> wrote:
>>>>>> 
>>>>>> Thanks Bert, I’ll check but I’m pretty sure I am. I’ll take a look at the test cases in question too to make sure its not the tests.
>>>>>> 
>>>>>> 
>>>>>>> On 13 Mar 2016, at 23:24, squeak-dev-request at lists.squeakfoundation.org wrote:
>>>>>>> 
>>>>>>> Are you using the latest trunk image? It should be fixed.
>>>>>>> 
>>>>>>> - Bert -
>>>>>>> 
>>>>>>> 
>>>>>>>> On 12.03.2016, at 09:45, Max Leske <maxleske at gmail.com> wrote:
>>>>>>>> 
>>>>>>>> Hi,
>>>>>>>> 
>>>>>>>> The Fuel builds for trunk are still failing because our tests with dates and timezones fail due to the recently diagnosed problem with date and time in the image (the topic was “trunk thinks it’s tomorrow”).
>>>>>>>> 
>>>>>>>> I haven’t seen any activity on that front in the last couple of days. What is the status? When can I expect this to be fixed? Or was it already fixed?
>>>>>>>> 
>>>>>>>> Cheers,
>>>>>>>> Max
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20160318/072fa745/attachment.htm