(In reply to comment #11)
Hi Christopher,
As you may have noticed, the bug should be fixed starting with version 4.0.3RC2.
Thank you for your reminder, which resulted in putting the bug fix forward from 4.1 to 4.0.3
(In reply to comment #11)
Hi Christopher,
As you may have noticed, the bug should be fixed starting with version 4.0.3RC2.
Thank you for your reminder, which resulted in putting the bug fix forward from 4.1 to 4.0.3