17-Apr-2016, 07:32
The new 1.5 / 1.7.1 versions still has this issue.
But support sent me a new version of 1.5 and it works without issues. So I guess they have fixed it, and we can expect it in the next udpate!
But support sent me a new version of 1.5 and it works without issues. So I guess they have fixed it, and we can expect it in the next udpate!
