+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: Support (/forumdisplay.php?fid=4)
+--- Thread: indexArtwork : feature request (/showthread.php?tid=7510)
Pages: 1 2
RE: indexArtwork : feature request - eseb63 - 24-11-2025 21:59
good news...
i am a bit confused for the first one ;
you say first :
(14-10-2025 12:55)simoncn Wrote: I am also seeing a similar problem with Recently Added not showing its custom image for its subcontainers.
so, as you say it's a problem, i understand the Recently Added custom image should be shown for its subcontainers
but you say later :
(15-10-2025 08:53)simoncn Wrote: Custom images for all index entries (including Last day, Last week, etc.) are available currently and will continue to be available, so the Last day index can have its own custom image file Last day.jpg. If this file isn't present, the Last day index will not inherit the custom image Recently Added.jpg. This inheritance of custom images is supported only for index entries for tag values in tag indexes. For example, the index entry Melissa Laveaux in the Artist index will inherit the Artist.jpg custom image if there is no Melissa Laveaux.jpg custom image.
and i understand the opposite, because it works for tag values but not for subcontainers, am i right?
So, what will be the correction for this Recent Added issue?
and what about folder view?
RE: indexArtwork : feature request - simoncn - 25-11-2025 11:06
In the next update, the Recently Added image will be shown for subcontainers of Recently Added unless it is overridden by a specifc subcontainer image (for example, Last week.jpg or 2025.jpg). These subcontainer images can be in the indexArtwork folder or in the RecentlyAdded subfolder of the indexArtwork folder, just like images for tag values such as Artist or Composer. The same applies to Recently Played.
The only change to folder view images is to fix a bug that prevented the image in [folder view].jpg being shown for the top-level [folder view] index.
The update will also fix the problem with incorrect images being shown for some index containers as described in this post.
RE: indexArtwork : feature request - eseb63 - 25-11-2025 12:28
(25-11-2025 11:06)simoncn Wrote: The only change to folder view images is to fix a bug that prevented the image in [folder view].jpg being shown for the top-level [folder view] index.will the subfolders inherit from the [folder view] custom image?
RE: indexArtwork : feature request - simoncn - 25-11-2025 20:43
Inheritance is only for tag indexes and Recently Added and Recently Played. This is because selecting any of these indexes shows another index list and inheritance provides default images for the contents of this index list.
Selecting other top-level indexes (n albums, n items, n playlists, [untagged] and [folder view]) shows a selection of library contents using artwork rules described in this section.
RE: indexArtwork : feature request - eseb63 - 26-11-2025 11:05
The leaf folders are managed by a folder.png image, but the intermediate folders are not: it's a bit of a shame to have to massively duplicate an image to reproduce inheritance when a single image would suffice (the one from the "folder view" top index, which would be the default image) ?
RE: indexArtwork : feature request - simoncn - 26-11-2025 12:48
I think this is part of a wider issue of making it possible to provide default images for all MinimServer selections. For example, there is no default image for an item or an album. This needs careful thought and I will add it to the list of requested features.
RE: indexArtwork : feature request - simoncn - 05-12-2025 11:42
The indexArtwork changes for Recently Added and Recently Played are now available in MinimServer update 264.
RE: indexArtwork : feature request - eseb63 - 05-12-2025 15:04
(05-12-2025 11:42)simoncn Wrote: The indexArtwork changes for Recently Added and Recently Played are now available in MinimServer update 264.
Thanks, it works...
Though, i noticed a behavior change for index artwork subfolders :
- before 264 update, the behavior is as explained in the User Guide
Note 1: If a tag name is translated or substituted for viewing in the index, the original tag name is used for the tag-specific subfolder name. - 264 update seems to break this rule ; the custom images of the tag subfolder are now only shown if the subfolder translated name is used.
it's a bit annoying because i wrote a script that follows the present rule and creates the subfolders with the original tag name and i would have to manage the translated names.
RE: indexArtwork : feature request - simoncn - 05-12-2025 17:28
Thanks for letting me know about this. I will look into it and post back here.
RE: indexArtwork : feature request - simoncn - 06-12-2025 20:54
This change was not intentional. It has happened as a side effect of my rewriting the code that handles this in order to resolve the problems and limitations in the previous implementation.
The previous implementation used translated names for top-level index images such as Compositeur.jpg and Conducteur.jpg and used English names for the corresponding subfolders Composer and Conductor. This is inconsistent and confusing. As a result of the rewrite, the subfolder names now match the image filenames. I think this is how it should work, even though it is a change from the previous implementation. The image filename and subfolder name now match the name that is shown in the index and I think this is preferable to having the image filename and subfolder name in English. My proposal is therefore to change the User guide description to match the current implementation.
I would not normally make a change like this to an existing user interface but in this case I think the simplicity and consistency of having all the names match justifies the change. I am sorry for the inconvenience this has caused you and possibly other users.