Thank you, that build does resolve the issue.
If you have the time, could you verify that the issue has not resurfaced in the latest version? (112)
Sorry for not noticing your question until now. The issue has not resurfaced in the latest version (113).
That's good, thanks for letting me know.
