Yeah, thats how i read it.Alan Phipps wrote: ↑Wed, 13. Oct 21, 13:15Well if the issue is here reported in 4.10 release and as yet there have been no updates/hotfixes since 4.10 release then the fix *must* be in a future build whether as an update or as a hotfix.
But i missunderstood your post.
My "fixed" referenced the unreleased development built.
So I meant "it's fixed, but not released"
Which is fine for me...