You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently using version 3.3 from Debian GNU/Linux 11 (bullseye) with the Flow View. Every time a host changes from 0/x to 1/x or more the font switches from normal to bold. When going back to 0/x the font switches back. The bold font obviously is wider than the normal font. If this happens to the longest entry in the host list, the whole column gets wider and less wide. If the job count on this host often changes from 0 to more and back this leads to some kind of column width flickering which is rather annoying.
I only have screenshots to show this, some kind of animated GIF or a video would better show what I mean, but maybe you understand my description and can reproduce it?
Maybe this was introduced with e22a5ef. At least that was the only change I could find between v3.0.0 and v3.3 touching this.
The text was updated successfully, but these errors were encountered:
Bad and also annoying side effect: every time the column widths change, the bars in the "History" column get reset, and you can not see a nice history, because the colorful bars disappear again and again.
Currently using version 3.3 from Debian GNU/Linux 11 (bullseye) with the Flow View. Every time a host changes from 0/x to 1/x or more the font switches from normal to bold. When going back to 0/x the font switches back. The bold font obviously is wider than the normal font. If this happens to the longest entry in the host list, the whole column gets wider and less wide. If the job count on this host often changes from 0 to more and back this leads to some kind of column width flickering which is rather annoying.
I only have screenshots to show this, some kind of animated GIF or a video would better show what I mean, but maybe you understand my description and can reproduce it?
Maybe this was introduced with e22a5ef. At least that was the only change I could find between v3.0.0 and v3.3 touching this.
The text was updated successfully, but these errors were encountered: