2023-05-26 03:01 PM
2024-02-16 01:00 AM
in the current version 2.15 it is still not fixed
It's a real shame, we're still using version 2.5! because none of the next versions solved the problem