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
On my Void Linux install, I have quite a few fonts installed through their google-fonts package among others. Unfortunately, this means that trying to pick a font to use in the application takes... a very long time (when I informally tested it, roughly two and a half minutes)!
In comparison, the gnome-font-viewer application has a noticeable delay but at most takes around 5-10 seconds to display the searched results.
Though, I should note that I have Folio installed via an AppImage and I have GNOME's font viewer installed through a traditional package. This alone could make a difference given the way the two models differ in terms of interacting with the system (at least, from my understanding).
The text was updated successfully, but these errors were encountered:
Folio just calls GTK's FontDialog() picker, so any lag is in GTK not Folio. Have you tried picking a font in another GTK app that used FontDialog()? (I know Pinta uses it)
If it acts the same, I doubt there's anything to be done about the slowness from Folio's side, you'd have to open a ticket with GTK.
On my Void Linux install, I have quite a few fonts installed through their
google-fonts
package among others. Unfortunately, this means that trying to pick a font to use in the application takes... a very long time (when I informally tested it, roughly two and a half minutes)!In comparison, the
gnome-font-viewer
application has a noticeable delay but at most takes around 5-10 seconds to display the searched results.Though, I should note that I have Folio installed via an AppImage and I have GNOME's font viewer installed through a traditional package. This alone could make a difference given the way the two models differ in terms of interacting with the system (at least, from my understanding).
The text was updated successfully, but these errors were encountered: