I just checked my ~/.local/share/Steam/userdata/*/config/grid/ folder, by running file * in the terminal. I found:
One empty file (0 bytes).
Several Targa image data files (all of them are icons, and they seem to be working fine; surprising for me because I didn't know that format was supported).
Eight HTML documents (i.e. somehow the image was not found and returned a 404 document instead).
BoilR doesn't support invalid images. When I tried to select the new logo to replace that empty file, I couldn't use BoilR interface, as the logo wasn't visible and wasn't clickable. I had to manually delete that file and then use BoilR.
Proposed solution 1
If a file is invalid (or has an absurdly small size, e.g. less than 32x32), the BoilR interface should display a large enough placeholder box so the user is able to click on it to replace it.
Bonus points for always having borders around each of the images (imagine someone accidentally installs a completely transparent image, how would the user be able to "see" it to click on it?)
Proposed solution 2
Additionally, BoilR could check all existing images for integrity. Any broken image (i.e. empty files, HTML files, non-image files, or even corrupted files) could be listed in a new panel (let's call it "house cleaning" or "issues" or "health check") in the UI, so that the user will be able to act on those broken files. Most likely, delete them, but possibly replace them with proper images.
I just checked my
~/.local/share/Steam/userdata/*/config/grid/folder, by runningfile *in the terminal. I found:BoilR doesn't support invalid images. When I tried to select the new logo to replace that empty file, I couldn't use BoilR interface, as the logo wasn't visible and wasn't clickable. I had to manually delete that file and then use BoilR.
Proposed solution 1
If a file is invalid (or has an absurdly small size, e.g. less than 32x32), the BoilR interface should display a large enough placeholder box so the user is able to click on it to replace it.
Bonus points for always having borders around each of the images (imagine someone accidentally installs a completely transparent image, how would the user be able to "see" it to click on it?)
Proposed solution 2
Additionally, BoilR could check all existing images for integrity. Any broken image (i.e. empty files, HTML files, non-image files, or even corrupted files) could be listed in a new panel (let's call it "house cleaning" or "issues" or "health check") in the UI, so that the user will be able to act on those broken files. Most likely, delete them, but possibly replace them with proper images.