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
Brisk Menu tries to re-size itself automatically so that the category sidebar doesn't show a scrollbar. With the default Arc theme that Solus MATE currently uses this works fine.
If I use the Adapta GTK theme (either the regular or ETA variant), then brisk menu always shows a scrollbar for the categories section (even though it's sized so that all the categories do show without the need to scroll). I've attached a screenshot example.
Note: If I apply the adapta theme, and then switch from Adapta to Adapta-ETA, the brisk menu is sized appropriately without showing a scrollbar. However, if I then reboot or logout/back in the scrollbar is back
The text was updated successfully, but these errors were encountered:
looks like this might be more obscure then it seemed.
It appears to be related to certain combinations of font size/dpi
With 120 dpi and interface font set to clear sans size 10, I get the issue (but oddly only with the adapta theme, the myriad of other themes I tried I got no scrollbar).
but If I either change my dpi to 96, or change the font size to 9 the scrollbar stops showing with the adapta theme
Running Solus 3 with all update (Brisk 0.5)
Brisk Menu tries to re-size itself automatically so that the category sidebar doesn't show a scrollbar. With the default Arc theme that Solus MATE currently uses this works fine.
If I use the Adapta GTK theme (either the regular or ETA variant), then brisk menu always shows a scrollbar for the categories section (even though it's sized so that all the categories do show without the need to scroll). I've attached a screenshot example.
Note: If I apply the adapta theme, and then switch from Adapta to Adapta-ETA, the brisk menu is sized appropriately without showing a scrollbar. However, if I then reboot or logout/back in the scrollbar is back
The text was updated successfully, but these errors were encountered: