Wrong filesize in 'Generate file listing'

[igor]

if xnview produces a file listing with the properties-box NOT checked, the filesize is wrong: it is the same for every file in the listing.
When the properties-box is checked, it's OK.

- os: Win2k
- xnview: tested on v1.80 and 1.80.3

[xnview]

if xnview produces a file listing with the properties-box NOT checked, the filesize is wrong: it is the same for every file in the listing.
When the properties-box is checked, it's OK.

Sorry i can't reproduce this bug, could you tell me which settings do you have?

[helmut]

if xnview produces a file listing with the properties-box NOT checked, the filesize is wrong: it is the same for every file in the listing.
When the properties-box is checked, it's OK.

Sorry i can't reproduce this bug, could you tell me which settings do you have?

I've also tried on Win 2000 and XnView 1.80.3 - no problems.

[igor]

steps to reproduce the bug on win2K v1.80.3:

- select some files in the browser
- 'generate file listing' (Shift+L)
- settings: checked 'size': size-type 'KB' (but problem occurs on other size-types as well)

result: notepad text-file with always 0 as result

However the different sizes return OK if the 'size'-checkbox is combined with 'properties' or 'type' or both.
--------------------------------
I also had the same problem on another computer, also win2K, but with v. 1.80: there the bug occurs on the same combination of checkboxen, but the returned sizes are not zero, but some other value (but I have no idea what this value is).

[xnview]

steps to reproduce the bug on win2K v1.80.3:

- select some files in the browser
- 'generate file listing' (Shift+L)
- settings: checked 'size': size-type 'KB' (but problem occurs on other size-types as well)

result: notepad text-file with always 0 as result

However the different sizes return OK if the 'size'-checkbox is combined with 'properties' or 'type' or both.
--------------------------------
I also had the same problem on another computer, also win2K, but with v. 1.80: there the bug occurs on the same combination of checkboxen, but the returned sizes are not zero, but some other value (but I have no idea what this value is).

Ok, i can now reproduce the problem...