Master on Windows 10

[Robert Fewell]

John,

I think I have found the problem, well may be the start, in
gnc-timezone.cpp on line 230, I think it should be max_year instead of 0.

If I change that, then Gnucash starts up but I think some thing else is
wrong also. If I create a new file with two transactions, one today and one
02/03/2016 before BST, they are stored in the xml files as follows, all
entered between 13:00 and 14:00 local time...

XFCE, Gnucash 2.6.11

date posted  2016-03-02 00:00:00 +0000
date entered 2016-05-02 13:31:39 +0100

date posted  2016-05-02 00:00:00 +0100
date entered 2016-05-02 13:31:24 +0100

Gnome VM, Gnucash Master

date posted  2016-03-02 00:00:00 +0000
date entered 2016-05-02 13:24:39 +0100

date posted  2016-05-02 00:00:00 +0100
date entered 2016-05-02 13:24:39 +0100

Win10, Gnucash Master

date posted  2016-03-02 00:00:00 -0100
date entered 2016-05-02 12:45:55 +0000

date posted  2016-05-02 00:00:00 +0000
date entered 2016-05-02 12:45:39 +0000

WinXP VM, Gnucash Master

date posted  2016-03-02 00:00:00 -0100
date entered 2016-05-02 12:55:46 +0000

date posted  2016-05-02 00:00:00 +0000
date entered 2016-05-02 12:55:32 +0000

Just looking for confirmation before I start looking further.

Robert


On 1 May 2016 at 18:25, John Ralls <jralls at ceridwen.us> wrote:

>
> > On May 1, 2016, at 9:34 AM, Robert Fewell <14ubobit at gmail.com> wrote:
> >
> > The comparison to Linux was the contents of zone_vector was being
> populated, I understand that it gets it gets populated differently but
> assume the information contained in zone_vector was the same.
>
>
> Bob,
>
> Well, sort of. Unix's database goes back to the beginning of time zones
> and IIRC Microsoft's goes back only to 1970 -- and only goes back at all
> starting with either XP SP3 or Vista. But there should always be at least
> one entry.
>
> My point was that you should be comparing the results on Win10 with those
> on Win7 because they both use the same code path.
>
> Regards,
> John Ralls