@sebavan
This is also one issue that I have that @louisnayegon also wants to fix in 4.2.1 version.
Regards Peter