We will work on improving this.
You are right, we will fix this.
We will work on improving this.
You are right, we will fix this.
@Tomek_Wloga this has been fixed in the last 2.2.1 release: VisualARQ 2 - Version 2.2.1 released
We have changed this behavior in VisualARQ 2.3 (VisualARQ 2 - Version 2.3 released)