Hi Milan,
We sincerely apologize for the inconvenience, and I completely understand your frustration. The recently released version 6.1.2 is primarily a bug-fix update for issues introduced in version 6.1.1.
As I mentioned earlier, the issue you reported was identified after version 6.1.1 had already entered the testing phase, which is why it wasn’t included in this release. However, our development team is aware of it, and it’s scheduled to be addressed in an upcoming version.
Thank you for your patience and understanding.