After updating to the latest version this morning, I confirm the bug has been fixed in the 1.4.2 release. Thanks a lot for your work.
After updating to the latest version this morning, I confirm the bug has been fixed in the 1.4.2 release. Thanks a lot for your work.