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
While migrating from Ubuntu 16.04 to 18.04 in my CI/CD environment, I suddenly discovered that my AppImage main icon is now a 48x48 image instead of a larger one. I started digging and found a couple of inconsistencies.
Correct me if I'm wrong, but as I see it, the initial idea of the main icon detection is to prioritize some images over the others (256x256 over 48x48, SVG over XPM, etc.). However, the current algorithm is using the foreach/continue construction which reassigns the iconToBeUsed variable until the last available (not the best) candidate is met.
Furthermore, it seems that QDirIterator is using readdir() under the hood, which doesn't guarantee a specific order, so it fully depends on a filesystem implementation. I don't think linuxdeployqt should rely on a random order of this iteration.
If you confirm my assumptions on the icon priorities, I'm ready to submit a pull request fixing this issue.
The text was updated successfully, but these errors were encountered:
While migrating from Ubuntu 16.04 to 18.04 in my CI/CD environment, I suddenly discovered that my AppImage main icon is now a 48x48 image instead of a larger one. I started digging and found a couple of inconsistencies.
Correct me if I'm wrong, but as I see it, the initial idea of the main icon detection is to prioritize some images over the others (256x256 over 48x48, SVG over XPM, etc.). However, the current algorithm is using the
foreach/continue
construction which reassigns theiconToBeUsed
variable until the last available (not the best) candidate is met.Furthermore, it seems that
QDirIterator
is usingreaddir()
under the hood, which doesn't guarantee a specific order, so it fully depends on a filesystem implementation. I don't thinklinuxdeployqt
should rely on a random order of this iteration.If you confirm my assumptions on the icon priorities, I'm ready to submit a pull request fixing this issue.
The text was updated successfully, but these errors were encountered: