Hi, Sorry to start this post again, but i am having the same issue mentioned above, with the latest release.Rseding91 wrote:Thanks for the report and investigation. It's now fixed for the next version of 0.16 or 0.17 which ever comes first.
Has the update containing the fix been done? Or will it only be in 0.17?