Page 1 of 1

1.4.0 (Windows 10): no hiding of companion files with a dot in the filename

Posted: Sat Jan 07, 2023 9:55 am
by thefrip
Hello,

I just realised that XnViewMP is not hiding files having a dot in their filename (on top of the extension dot one I mean). I attach a screen copy of the problem:

Screen-2023-01-07_10-45-40.jpg

The folder shows twice the same photo, once with dots in the filename (to split the time of the day of the photo) and once with dashes replacing the dots. The companion file (rw2, raw Panasonic file) is shown in the first case, hidden in the second one (setting is of course off for Showing companion files).

Rgds,

L.

Re: 1.4.0 (Windows 10): no hiding of companion files with a dot in the filename

Posted: Mon Jan 09, 2023 12:11 pm
by xnview
:bugconfirmed: Thanks to your detailed description I can reproduce

Re: 1.4.0 (Windows 10): no hiding of companion files with a dot in the filename

Posted: Sat Jan 28, 2023 3:10 pm
by ewsb
Although this is a very old problem - I am still getting it in 2023 on V1.4.2?

Re: 1.4.0 (Windows 10): no hiding of companion files with a dot in the filename

Posted: Thu Apr 27, 2023 1:29 pm
by Gwenael Q.
Hello,

Is this issue fixed ?

I can not reproduce here (jpegs and NEF, but with NEF as master)

Thanks for listening

1.4.4

Re: 1.4.0 (Windows 10): no hiding of companion files with a dot in the filename

Posted: Fri Jun 07, 2024 1:42 am
by spaceNpace
I am able to reproduce this issue in 64-bit version 1.7.2 running on Windows 10.

The following are additional issues that have been reported with linked companion / sidecar files:

Re: 1.4.0 (Windows 10): no hiding of companion files with a dot in the filename

Posted: Wed Apr 30, 2025 7:01 am
by xnview
do you have always this problem in 1.8.8?

Re: 1.4.0 (Windows 10): no hiding of companion files with a dot in the filename

Posted: Tue May 06, 2025 9:44 pm
by spaceNpace
In XnView MP 1.8.8 64-bit running on Windows 10, it appears the issue of companion files not being hidden when the filename contains a dot has been addressed.

While testing, I did also go ahead and check the linked companion file issue linked in an preceding post, but it appears that remains outstanding.