On 25-10-2018 8:39, Thomas de Groot wrote:
> Well, it definitely was an issue with versions 3.6 and below, and, as > far as I recall, with version 3.7.>
Just to confirm, after testing: Also an issue with version
3.7.0.msvc10.win64
The correction must have been made in one of the 3.8.0 alphas.
--
Thomas
