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
I rarely have simple and short filenames. The UI is extremely wide because of this, and requires resizing the window's width to somewhat unreasonable sizes in order to be able to see all columns, namely the "Output size" to see how efficient the result was.
I mean, it barely fits on my 2560px-wide screen, and yet I typically do not want a small utility app's window to take more than half of my screen width, it's supposed to be a companion app rather than a centerpiece.
I'm not sure how to solve this elegantly, but here are some ideas.
I'm not sure the "output image" column is useful at all. But if it is, consider putting that text on a 2nd line below the "input image" text string, separated by a line break character, and using some 50% opacity for the 2nd line or something...
The Input size and Output size columns should be grouped next to each other, I think those are the most important pieces of information. So move the "Output size" column to be right after "Input size", or put its information on a 2nd line using a linebreak?
The text was updated successfully, but these errors were encountered:
Yes you are right, the UI is quite basic currently, I have to improve it. I am not sure when I will work on it, but it is on my TODO list for a future version :)
Running the Flathub flatpak version.
I rarely have simple and short filenames. The UI is extremely wide because of this, and requires resizing the window's width to somewhat unreasonable sizes in order to be able to see all columns, namely the "Output size" to see how efficient the result was.
I mean, it barely fits on my 2560px-wide screen, and yet I typically do not want a small utility app's window to take more than half of my screen width, it's supposed to be a companion app rather than a centerpiece.
I'm not sure how to solve this elegantly, but here are some ideas.
The text was updated successfully, but these errors were encountered: