1.91.5: Prev / Next buttons active if only 1 file in dir

[spacemarine]

Minor cosmetic bug, steps to reproduce:

1) There is only one, single viewable file (e.g. example.jpg) in
a directory.

2) Open the file in XnView's viewer by double-clicking in the explorer

3) The arrow buttons Previous file / Next file on the toolbar are active and
clickable, though nothing happens when you click on them.

Expected behaviour:

The buttons should be inactive and "greyed out" if there are no previous /
next files in the dir.

[Clo]

—> spacemarine

Hello !

• Right, but we have the same behaviour in all old versions (I checked it even in 1.80.3).
- Both buttons might be greyed out - logically - but maybe Pierre has a good reason to leave that “as is” ?

VG
Claude
Clo

[spacemarine]

Strangely, when you then click on any dropdown menu, the
buttons then become greyed out and inactive.

Does this also happen for you ?

[Clo]

—> spacemarine

Hello !

• Yes, it does ! In all versions I tested.

- The mystery darkens…

VG
Claude
Clo

[XnTriq]

Eh, but when you open the first image, go one image forward and one image backward, the "Previous file" button is correctly grayed out. So why does this work then? Does XnView known how many images there are by one looking at the first two?

Honestly, this should not be impossible to fix. Other image viewers can to so, too.

It's for speed, i load list of files only if you click on next/previous!

Possibly also related: [Minor] “Next file” button not greyed… (Resolved Bugs & Requests)

[spacemarine]

So maybe this can be changed in a future version ?

No hurry needed, but I think before adding new features, small
glitches such as this one should be corrected first

Cheers,
Spacemarine

[Clo]

—> XnTriq

Hello Me. Librarian !

• The bug I reported in the thread you quote is back in 1.91.5, exactly like decribed there.

• Pierre, pleaaaaaase ?

KR
Claude
Clo

[xnview]

—> XnTriq

Hello Me. Librarian !

• The bug I reported in the thread you quote is back in 1.91.5, exactly like decribed there.

• Pierre, pleaaaaaase ?

The problem is: When you open a file, i don't know how many files are on the same folder! I check only when only you click on next or previous

[spacemarine]

But then why do the prev / next arrows become greyed out (=inactive)
when you simply click on any dropdown menu in the main menu toolbar ?

That seems mysterious to me .... does some kind of file check (whether there
is more than one file in the directory) take place when you click on a menu ?

[xnview]

But then why do the prev / next arrows become greyed out (=inactive)
when you simply click on any dropdown menu in the main menu toolbar ?

That seems mysterious to me .... does some kind of file check (whether there
is more than one file in the directory) take place when you click on a menu ?

You have a folder with only 1 file, and you open it. The prev/next button are active, you click on any toolbar menu, and they become greyed??? I can't reproduce...

[Clo]

—> Pierre

Hello !

• Like I confirmed already above, this occurs here too with XP-Pro SP1, and the two buttons turn greyed
even simply clicking anywhere on the background of the window in “View” !
- Indeed also opening any menu, like spacemarine said…

KR
Claude
Clo

[spacemarine]

Yes, just as Clo also confirmed.

If clicking on any menu (or on the background, as Clo said)
with only one viewable file in a directory both arrow buttons
become greyed.

With two or more images in the folder, depending on which of the images you are viewing
(which one you click on in the explorer to start XnView),
the "previous" OR the "next" button OR neither of the two
becomes greyed (which is the correct behaviour in each case).

Some checking must take place then
So just do this check at the program start, and the problem is solved

Maybe it has to do with our view settings ? I only allow XnView to show
images (nothing else), and I have set it to only use one view window
(i.e. reuse the same window), and multiple program instances are also
not allowed. "Read one image ahead" AND "keep current image" in cache are both selected.
Of course some other setting could be the culprit which causes this
behaviour, but right now I can't imagine which one

Cheers,
Spacemarine