Yo,
We picked up on this issue some time ago (don't remember when, doesn't matter) and it happens to already be fixed in our internal version, meaning it'll be OK for everyone at next version release.
Cheers,
Arthur
We picked up on this issue some time ago (don't remember when, doesn't matter) and it happens to already be fixed in our internal version, meaning it'll be OK for everyone at next version release.
Cheers,
Arthur