Hi,
I can confirm that this bug still exist in version 5.4.10.Final
any news about this?
Regards,
Nelson.