06-18-2016, 04:25 PM
It's possible I fixed it after the release of v1.5.3, but then committed my changes under source control as version 1.5.3, confusing myself as to when I made them. I think it will be fixed in v1.5.4 then... we will see.
Thanks,
Mike
Thanks,
Mike