Print file via command line: filename is missing

[critesta]

Hello. I'm trying to use XnView via command line to print a set of images with the following syntax:
xnview.exe /print <filename>
Everything is working fine except for caption informations:
I have set caption to <Filename With Ext> at bottom of the page and I've found this problem:
- when I open the file with xnview and print it via the GUI the filename is correctly printed at the bottom of the page
- when I use the command line xnview.exe /print the file is printed but without the caption informations.

The ini file is set as follows:


[Print]
AllPages=0
AutoRotate=1
BottomMargin=0.20
CType=0
Columns=4
EFontBold=0
EFontHeight=10
EFontItalic=0
EFontName=Courier
ETextColor=0
FText=Page <Page Number>/<Page Count>
First=1
FontBold=0
FontHeight=10
FontItalic=0
FontName=Arial
Gamma=1.00
HText=
Height=10.00
HoriSpacing=1.00
JobPerPage=0
KeepRatio=1
Last=1
LeftMargin=0.20
Multiple=0
Option=0
Position=4
RightMargin=0.20
Rows=4
Text=<Filename With Ext>
TextColor=0
TextPosition=1
TextUse=1
TopMargin=0.20
Units=0
UseFooter=0
UseHeader=0
VertSpacing=1.00
WFontBold=0
WFontHeight=10
WFontItalic=0
WFontName=Courier
WFontOrientation=0
WOrientation=0
WText=
WTextColor=0
WTextPosition=0
WUse=0
Width=10.00
XScale=2.00
YScale=2.00

Am I doing something wrong?
Thank you

[helmut]

The missing caption sounds like a bug to me.

[wawpeter]

Hello. I'm trying to use XnView via command line to print a set of images with the following syntax:
xnview.exe /print <filename>
Everything is working fine except for caption informations:
I have set caption to <Filename With Ext> at bottom of the page and I've found this problem:
- when I open the file with xnview and print it via the GUI the filename is correctly printed at the bottom of the page
- when I use the command line xnview.exe /print the file is printed but without the caption informations.

I am having a similar issue to critesta, any ideas about this bug anyone?

[xnview]

I am having a similar issue to critesta, any ideas about this bug anyone?

with 2.00?