I'm not sure how the core would know about skin-specific overlays. In my skins, that information isn't even stored in the .info files. The fact that a thumbnail is going to be given an overlay isn't known until the skin is actually iterating through the files.
The idea is just for a warning, not for a general usage. I was thinking of an api call on an album object that would add the icon/overlay. If the skin code shows an image is too small then an api call sets the icon/image (think of the warning triangle icon and folder overlay).
For an icon/overlay the skin could supply its own in the skin folder or call up a default, like the skin icon and warning triangle.
Edited by: RobM on 14 May 2022, 18:30
To add more information. A skin could apply the api call at any point to update the explore display. For a critical skin problem the image could even be selected in the gui and the build stopped. Non critical problems could just mark the objects and present a message.
