Often I have corresponding raw and jpg files in the same dir, both showing the same subject but at different resolutions. When I browse these pictures, I essentially view every subject 2 times, wich is a timewaste. An option to display (configurable for browser, viewer and fullscreen) only either the jpgs or the raws would be good for this case. The best criteria would probably be the filename.
Basically an option wich extension to exclude from viewing, IF files with same base name AND different extension exists. General case could be implemented as a list of extensions where the first in the list is the one to display.
Configurable viewing exclusion
Moderators: helmut, XnTriq, xnview
Ignore dupe---
plarry
Hello !• I get you issue. I guess that such a function should need a dialogue, IMHO so easy to design as GUI,
but a so big deal to realize about the addition of codes in the core…
- It's indeed useful and missing currently though, so I support the idea.
- I'll try to draw a mock-up if possible…
… Let's say, something like this :
KRClaude
Clo
Old user ON SELECTIVE STRIKE till further notice •
Hello Clo and ouistiti!
Yes, adding this in the code is the real work. If its not to be added then of course I respect that, XNView is free after all. But aside from this, nice to see that you would like to get this added too.
I like the GUI, especially the short explanations! I had something like this in mind:
I Imagine that as a part of the GUI. The first item would be displayed, the other excluded. Simpler to define, but harder to explain. One could mark the first with differing color. Also What I dont like in your Gui sketch Clo are the different options for fullscreen normal view and browser, that would make up for a big mess imho. (Well ok at least I could set it to show everywhere the same so it wouldnt hurt to include it.)
All the best!
Christian
Yes, adding this in the code is the real work. If its not to be added then of course I respect that, XNView is free after all. But aside from this, nice to see that you would like to get this added too.
I like the GUI, especially the short explanations! I had something like this in mind:
I Imagine that as a part of the GUI. The first item would be displayed, the other excluded. Simpler to define, but harder to explain. One could mark the first with differing color. Also What I dont like in your Gui sketch Clo are the different options for fullscreen normal view and browser, that would make up for a big mess imho. (Well ok at least I could set it to show everywhere the same so it wouldnt hurt to include it.)
All the best!
Christian
More flexible…
plarry Hello !
• We know that kind of syntax, it's used i.e. in Total Commander @ various uses like :…I Imagine that as a part of the GUI. The first item would be displayed, the other excluded.…
Process…|ignore…
- Such a function must fit the most needs for the most users, I guess.
Hence, a small box should be handier and more user-friendly.
• For instance, I could whish to ignore dupes in View and¦or Browser for small images like icons (I have a lot),
when they have duplicates as *.BMP-sources. No concern with full screen…
- Paul could have images of frames for some animations, and show *.PNG ones,
while he has *.BMP and *.GIF as duplicates.
- Another user could have large images and use the ignore feature in all modes…
- That's more flexible. Like you say too, implementing that is not a piece of cake, I suppose.
- Since the choices will land in the INI file as entries finally, we could hope such extra entries
as a first step when the appropriate codes are added…
• Now, we have to wait for the Pierre's opinion…
KRClaude
Clo
Old user ON SELECTIVE STRIKE till further notice •
Companion file & Companion concept
I think the above problem has a general nature: It's the handling of companion files. In the recent past, we have handled the deletion of companion files, this post is about viewing companion files.
Perhaps it's time to have a closer look at the various needs regarding companion files and then draft a larger and mature concept. For example, there could be an option page to administer companion files and set their behaviour:
- Browser -
(o) Display both files
( ) Display normal view, only
( ) Display preview, only
- Image view: Navigation -
(o) Navigate over both files
( ) Show normal views, only
( ) Show previews, only (?)
- Open -
(o) Open selected
( ) Always open normal view
( ) Always open preview (?)
- Delete -
[x] Delete companion file
Note: Options marked with (?) may not make sense in practice.
These are just some ideas and thoughts, the discussion is open, now.
Perhaps it's time to have a closer look at the various needs regarding companion files and then draft a larger and mature concept. For example, there could be an option page to administer companion files and set their behaviour:
- Browser -
(o) Display both files
( ) Display normal view, only
( ) Display preview, only
- Image view: Navigation -
(o) Navigate over both files
( ) Show normal views, only
( ) Show previews, only (?)
- Open -
(o) Open selected
( ) Always open normal view
( ) Always open preview (?)
- Delete -
[x] Delete companion file
Note: Options marked with (?) may not make sense in practice.
These are just some ideas and thoughts, the discussion is open, now.
Actually, the issue is even deeper. I frequently have same-named images in 3 or more different formats. Which of these should be displayed?
Perhaps if XnView had a mode that automatically stacked files of the same name (but different extensions) and we could then select which image is "on top" of the stack, XnView would default to displaying the file "on top"...
Stacking discussion is here.
Perhaps if XnView had a mode that automatically stacked files of the same name (but different extensions) and we could then select which image is "on top" of the stack, XnView would default to displaying the file "on top"...
Stacking discussion is here.
John
OK I could actually see another use.
Let the Autoamtic USB handler copy different fileformats to different subfolders. For example, copy to "2008_02_01\jpg\" and "2008_02_01\cr2\". Just a timesaver. Would need to be turned of by default.
I see this is a bit different, but still fits in the scope of dealing with companion files.
Curious to hear more ideas.
Let the Autoamtic USB handler copy different fileformats to different subfolders. For example, copy to "2008_02_01\jpg\" and "2008_02_01\cr2\". Just a timesaver. Would need to be turned of by default.
I see this is a bit different, but still fits in the scope of dealing with companion files.
Curious to hear more ideas.
Re: Companion file & Companion concept
Yes it's companion file, but all these settings for that??helmut wrote: - Browser -
(o) Display both files
( ) Display normal view, only
( ) Display preview, only
- Image view: Navigation -
(o) Navigate over both files
( ) Show normal views, only
( ) Show previews, only (?)
- Open -
(o) Open selected
( ) Always open normal view
( ) Always open preview (?)
- Delete -
[x] Delete companion file
For me, we need only 'show companion files' and a tab to set companion files (currently only in ini). It's difficult to say which extension is the normal view, the preview, ....???
Pierre.
Re: Companion file & Companion concept
"Browser" and "Image view: Navigation" are both filters and might be combined. Actually when thinking about it I see that the same could be achieved by setting the existing filter properly (Tools > Options | Browser > File List).xnview wrote:Yes it's companion file, but all these settings for that??
So all that is left:
- On Open -
(o) Open selected
( ) Always open normal view
( ) Always open preview (?)
- On Delete -
[x] Delete companion file
One challenge is to decide which is the original and which the companion file (preview). I guess an almost 100% and simple indicator would be the file size.