Just a note to say this is still an issue after upgrading to Pro 3.0
Hi Daniel,
Thanks for the heads up. It wasn’t an issue we were able to complete for this cycle, but we will be looking into it for the next update.
Great! Looking forward to it. Assume you can’t give me an ETA?
Regretfully I can’t give an ETA right now.
1 Like
Hi @dfinch,
You’ll find this fixed in the first point release of the current release cycle. This could be going out as early as this evening.
1 Like
You’re most welcome!
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
