Page 1 of 1
Import and sort - New filename - Cannot open destination file
Posted: Sun Apr 03, 2022 12:12 pm
by lomik_xp
Hello. Great app.
When I using "Import and sort" feature and choosing "New filename" with this value "{Folder name}\{EXIF:Date Taken [Y-m-d H-M-S]}"
then get error "Cannot open destination file". All rights have.
If I create folder myself then where is no error.
Re: Import and sort - New filename - Cannot open destination file
Posted: Sat Apr 09, 2022 12:38 pm
by helmut
lomik_xp wrote: Sun Apr 03, 2022 12:12 pm
Hello. Great app.
When I using "Import and sort" feature and choosing "New filename" with this value "{Folder name}\{EXIF:Date Taken [Y-m-d H-M-S]}"
then get error "Cannot open destination file". All rights have.
If I create folder myself then where is no error.
There's a field "Destination" and a field "Filename". In "Destination" you are supposed to specify the
destination folder and in "Filename" the (new) filename. In your case you specify both a folder and a filename in "Filename". This seems to work in some way but as we can see it doesn't work 100%. Please split folder information and filename into the fields "Destination" and "Filename" and I assume that your problem will dissappear.
Re: Import and sort - New filename - Cannot open destination file
Posted: Sat Apr 09, 2022 3:39 pm
by lomik_xp
It doesnt work.
May be not enough "mkdir" command programatically, because hint say it subfolders must work in filename.
I think its a bug.
Re: Import and sort - New filename - Cannot open destination file
Posted: Sat Apr 09, 2022 3:41 pm
by lomik_xp
Here is error like.

- 3_error.png (28.81 KiB) Viewed 765 times
Re: Import and sort - New filename - Cannot open destination file
Posted: Sat Apr 09, 2022 5:05 pm
by lomik_xp
XnView MP Windows
Version 0.99.7 64bits (Jan 13 2022)
Libformat version 7.100
Re: Import and sort - New filename - Cannot open destination file
Posted: Sat Apr 09, 2022 8:25 pm
by helmut
Thank you for your additional info, lomik_xp. I could reproduce your behaviour but I don't think that this is a bug:
I'm not 100% familiar with the "Import and sort" utility, but I think the hint "Here the filenames will be transfered. Subfolders will be created" is misleading and wrong. Subfolders will be created as specified in field "Subfolder". But I think that one must not use placeholder "{Folder name}" and backslash(es) in "New filename" field. Please remove "{Folder name}\" and see what happens.
Re: Import and sort - New filename - Cannot open destination file
Posted: Sun Apr 10, 2022 6:16 am
by lomik_xp
Yes its work, but not how I wanted

There is now two ways for this topic,
- its is bug and hint is not correct,
- its not bug, but suggestion and need add subfolders creation, and hint is confusing.
Re: Import and sort - New filename - Cannot open destination file
Posted: Sun Apr 10, 2022 6:21 am
by lomik_xp
As a programmer I would preferred this topic be a suggestion and implemented, this is simple.
Re: Import and sort - New filename - Cannot open destination file
Posted: Sun Apr 10, 2022 7:42 pm
by helmut
Thank you for your feedback, lomik_xp.
lomik_xp wrote: Sun Apr 10, 2022 6:21 am
As a programmer I would preferred this topic be a suggestion and implemented, this is simple.
I understand. As a user I would prefer a clean user interface.

Let's try and find a way to provde required functionality combined with a clean and intuitive user interface.
From my point of view the field "subfolder" should be more flexible and allow for entering subfolders or make use of the placeholder {Folder name}. Whereas the "New filename" is for specifying a filename - backslashes or placeholder {Folder name} shouldn't be allowed in that field.
Alternatively, both fields "subfolder" and "New filename" might be combined but I think this would make things less intuitive.
Re: Import and sort - New filename - Cannot open destination file
Posted: Mon Apr 11, 2022 3:55 am
by lomik_xp
Yes, user friendly interface is always must be in priority.
As example here (on screenshots) is "Videos" group with "Subfolder" field, just do it like there and write "mask" there, it's will be intuitively and clear.
In total, I may close bug and make a suggestion?