Page 1 of 1
A: Pictures from an folder are saved in previous folder
Posted: Fri Oct 13, 2006 12:51 pm
by decii
If you have two directories: Dir1 and Dir2 with the pictures.
In Dir1: in browser mode, select all pictures > CTRUL + U > Transformations > Resize all pictures
Go to in Dir2: do the same things, but the XnView save these files in Dir1, not in Dir2.
PS: Sorry for my english.
Re: Pictures from an folder are saved in previous folder
Posted: Fri Oct 13, 2006 1:20 pm
by xnview
decii wrote:If you have two directories: Dir1 and Dir2 with the pictures.
In Dir1: in browser mode, select all pictures > CTRUL + U > Transformations > Resize all pictures
Go to in Dir2: do the same things, but the XnView save these files in Dir1, not in Dir2.
PS: Sorry for my english.
Do you enter an output pathname?
Re: Pictures from an folder are saved in previous folder
Posted: Mon Oct 16, 2006 11:00 am
by xnview
decii wrote:Re: Do you enter an output pathname?
Where?
I was in browser mode. Perhaps I was't clear when I explain the bug:
- In Dir1 I have the same files like in Dir2.
Do you need the ini file (the file with XnView configuration)?
Do you set the output folder in the 'Batch convert' dialog
Posted: Mon Nov 27, 2006 10:43 pm
by helmut
Could not be reproduced in alpha 1. If no output folder is specified, XnView must use the current directory (which works fine for me).
decii could you please check whether you have specified an output folder?
Re: Pictures from an folder are saved in previous folder
Posted: Tue Nov 28, 2006 1:01 pm
by decii
[quote="xnview"][quote="decii"]Re: Do you set the output folder in the 'Batch convert' dialog?
No. It is not need. I tested again and the problem is fixed in beta 1.
Posted: Tue Nov 28, 2006 1:03 pm
by decii
helmut wrote:Could not be reproduced in alpha 1. If no output folder is specified, XnView must use the current directory (which works fine for me).
decii could you please check whether you have specified an output folder?
I don't specified the Output Directory - the field was empty. I tested again and the problem is fixed in beta 1.