Page 1 of 1

1.3.0: Custom image extensions and/or "Include" back-fordward navigation

Posted: Sat Oct 01, 2022 12:41 pm
by Marsu42
XnView: MP 1.3.0 - 64 bit
OS: Windows 10 64bit

I'm using an app which uses a custom image extension - .vtx are jpeg files with some custom metadata. I've added this extension to the "include" extension list, but navigation back/fordward (with cursor keys os the mouse wheel) when viewing an image doesn't work.

Effect: To view another .vtx image, it's necessary to close the image and select another image from with "Browser".

To reproduce:
1. Put some jpg files into a folder
2. Rename the extenions to vtx
3. Add vtx to the "Include" extension list
4. Open a vtx image
5. Try to view the previous/next vtx image using back-fordward navigation

Actual behaviour (bug): back-forward navigation is impossible, the Viewer is stuck on the current image :bug:

Expected behaviour: back-fordward navigation moves the Viewer to the previous or next .vtx image, like it's with .jpg

=> A solution might be be to enable custom extensions for images (it's only possible for Audio/Video/...) if this fixes navigation.

Re: 1.3.0: Custom image extensions and/or "Include" back-fordward navigation

Posted: Sun Oct 02, 2022 8:26 am
by masterjp
I can confirm this wrong behaviour of XnViewMP.

Re: 1.3.0: Custom image extensions and/or "Include" back-fordward navigation

Posted: Sun Oct 02, 2022 1:46 pm
by xnview
'include' can't be used for that. Try to disable 'Settings>File list>Recognize only by extension'?

Re: 1.3.1: Broken back-fordward navigation for non-default image extensions

Posted: Sat Oct 15, 2022 6:35 pm
by Marsu42
xnview wrote: Sun Oct 02, 2022 1:46 pm 'include' can't be used for that. Try to disable 'Settings>File list>Recognize only by extension'?
I've disabled "Recognize only by extension" and the .vtx files (i.e. every extension which is an image) show up without adding the extension to the include list.

However, back-fordward navigation with the mouse or keys is still broken, the image viewer is still stuck on the same image.

Any solution would be very welcome - I guess disabling "Recognize only by extension" probably slows down scanning, and I'm wondering what the "Include" filter is for if not for including extensions :-)