Overlay icon for sidecar files – Part deux

[XnTriq]

XnView MP v0.99.4 (64-bit) @ Windows 10 Pro 21H1

1. Create a new sub-folder in your XnView installation directory (e.g. C:\Program Files\XnViewMP\) named icons.
2. Download the following attachment (info@2x.png) to C:\Program Files\XnViewMP\icons\.
   info@2x.png
3. Download photo-4iptc-heads.jpg (e.g. to X:\Test\).
4. Create a copy of photo-4iptc-heads.jpg in X:\Test\ and rename the copy to photo-4iptc-heads_sidecar.jpg.
5. Save the following “code” as X:\Test\photo-4iptc-heads_sidecar.xmp:

   Code: Select all

   <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="XMP Core 6.0.0">
   	<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
   		<rdf:Description rdf:about="" xmlns:tiff="http://ns.adobe.com/tiff/1.0/">
   			<tiff:Orientation>4</tiff:Orientation>
   		</rdf:Description>
   	</rdf:RDF>
   </x:xmpmeta>

6. Create links to photo-4iptc-heads.jpg and photo-4iptc-heads_sidecar.jpg in the same folder.
7. Open Display in the Windows 10 settings (WinKey+I) and change Scale and layout to 125%.
8. Launch XnView MP.
9. Make sure that all checkboxes in Tools → Settings… → Thumbnail → Overlay icons is activated.
10. Point XnView's browser to X:\Test\.

Bugs / issues:

1. The overlay icon for face recognition is missing on the thumbnails of photo-4iptc-heads.jpg.lnk and photo-4iptc-heads_sidecar.jpg.lnk
2. There's (almost) no gap between the overlay icon for face recognition and the icon next to it

browser_thumbnails.png

browser_details.png

[xnview]

There's (almost) no gap between the overlay icon for face recognition and the icon next to it

Thanks to your detailed description I can reproduce the problem.

The overlay icon for face recognition is missing on the thumbnails of photo-4iptc-heads.jpg.lnk and photo-4iptc-heads_sidecar.jpg.lnk

No, because in this case, the .xmp is used, no more the embedded xmp

[XnTriq]

The overlay icon for face recognition is missing on the thumbnails of photo-4iptc-heads.jpg.lnk and photo-4iptc-heads_sidecar.jpg.lnk

No, because in this case, the .xmp is used, no more the embedded xmp

OK, makes sense!