User interface History: displayed times are not localized about multiminer HOT 7 CLOSED

Are you absolutely sure about this? I can look into it but I've never heard a report like this and would be pretty surprised to find this is true. The app uses standard .NET functions to get the current date & time.

from multiminer.

I can take a screenshot, but it's reporting both start and end times that are in my future! The most recent entry shows a Start time of 11:04pm today and an end time early tomorrow, and it's only 8:49pm here right now!

from multiminer.

Can you please check the Process Log and API Monitor screens as well? Are those times correct or incorrect? And yes screenshots would help (a picture is worth 1,000 words...) thanks!

from multiminer.

The times in the Process Log tab are probably correct, and the API Monitor tab definitely has localized times, so it appears that it's just the History tab that thinks it's in Greenwich or New York.

from multiminer.

Really at a loss here. Here is the start date being set:

        minerProcess.StartDate = DateTime.Now;

Here is the end date:

        DateTime endDate = DateTime.Now;

These are using DateTime.Now (same thing used throughout the app) and I'm not seeing code that would affect the time from there.

Can you shoot me an email and maybe we can work out a time to do a TeamViewer session?

from multiminer.

I was going to ask if the atypical date configuration I'm using in Windows (7) could be causing it, but it's only the one element that is affected... so I got nuthin'. I just sent a message to your domain.

from multiminer.

Worked through via TeamViewer - everything is looking right currently. Could be due to confusion about History records only being added once the user stops mining.

from multiminer.