1.5.2: Empty "Size" label is not hidden when "File Type" is presented

Reported bugs that have been closed and/or resolved

Moderators: helmut, XnTriq, xnview, Dreamer

Post Reply
User avatar
sad comrade
Posts: 2
Joined: Thu Aug 03, 2023 2:05 pm

1.5.2: Empty "Size" label is not hidden when "File Type" is presented

Post by sad comrade »

XnView: MP 1.5.2 - 64 bit
OS: Windows 64bit

Empty (({Size})) label is not hidden when there is a {File Type} label on the same line.

Effect: Size is displayed as "0 Bytes"

To reproduce:
1. Go to Settings > Thumbnail > Labels
2. Add a custom labels line:

Code: Select all

foo (({File Type})) (({Size}))
3. Add another custom labels line:

Code: Select all

foo (({Size}))
4. Confirm setting change
5. Examine thumbnails for a file and for a directory

Actual behaviour (bug):
  1. "foo (({File Type})) (({Size}))" is displayed:
    1. for directory as foo··0·Bytes ("·" is a space character)
    2. for file as foo·JPG·207.03·KiB
  2. "foo (({Size}))" is displayed:
    1. for directory as ·
    2. for file as foo·207.03·KiB
Expected behaviour: Empty (({Size})) should be hidden disregarding of other labels presence - "foo (({File Type})) (({Size}))" > "foo". Also it's kind of strange that foo is removed from result of "foo (({Size}))" if Size is empty
User avatar
xnview
Author of XnView
Posts: 46235
Joined: Mon Oct 13, 2003 7:31 am
Location: France
Contact:

Re: 1.5.2: Empty "Size" label is not hidden when "File Type" is presented

Post by xnview »

:bugconfirmed: Thanks to your detailed description I can reproduce the problem.
Pierre.
User avatar
xnview
Author of XnView
Posts: 46235
Joined: Mon Oct 13, 2003 7:31 am
Location: France
Contact:

Re: 1.5.2: Empty "Size" label is not hidden when "File Type" is presented

Post by xnview »

This problem is supposed to be fixed in XnView MP 1.5.4. Please check and confirm the bug fix here.
Pierre.
User avatar
sad comrade
Posts: 2
Joined: Thu Aug 03, 2023 2:05 pm

Re: 1.5.2: Empty "Size" label is not hidden when "File Type" is presented

Post by sad comrade »

I confirm the bug has been fixed in 1.5.4
Post Reply