Page 1 of 1

1.6.5 - Import & Sort: NO Dummy, moody etc.

Posted: Mon Mar 11, 2024 9:19 am
by m.Th.
There is a bug in the new Import & Sort engine. Because the letters „m, d, y” have special meanings, we cannot enter as custom destination folders words which contain at least one of these letters because they are replaced with the actual numerical values.

So if I have the following custom folder name:
Import and sort.png
The name of the resulting folder will NOT be „Dummy” but a mix of letters and numbers.

I think that the easiest solution is to add a checkbox under the name of the folder with the label „Folder name has special characters”. If the checkbox is checked („On”) then the behavior will be as it is now. If the checkbox is NOT checked („Off”) then the folder name will not be processed by the function which replaces the special characters.

The value of this checkbox should be saved between the sessions.

Re: 1.6.5 - Import & Sort: NO Dummy, moody etc.

Posted: Mon Mar 11, 2024 10:59 am
by user0
you should have posted this in your own request thread, which is in Retest section for a reason

Re: 1.6.5 - Import & Sort: NO Dummy, moody etc.

Posted: Mon Mar 11, 2024 12:45 pm
by xnview
what about using same separator [] like new filename? '[yyyy/MM] dummy'

Re: 1.6.5 - Import & Sort: NO Dummy, moody etc.

Posted: Mon Mar 11, 2024 2:38 pm
by user0
whatever you choose, it should be applied to 'Video subfolder' as well
I would go a little bit further:
import_subfolders.png

However, it's better to have single tag system, without splitting to {} and []

Re: 1.6.5 - Import & Sort: NO Dummy, moody etc.

Posted: Mon Mar 11, 2024 2:50 pm
by m.Th.
xnview wrote: Mon Mar 11, 2024 12:45 pm what about using same separator [] like new filename? '[yyyy/MM] dummy'
Very good solution.

Re: 1.6.5 - Import & Sort: NO Dummy, moody etc.

Posted: Tue Mar 12, 2024 9:31 am
by xnview
See issue for current status and some details.

Re: 1.6.5 - Import & Sort: NO Dummy, moody etc.

Posted: Thu Mar 28, 2024 1:43 pm
by xnview
This problem is supposed to be fixed in XnView MP 1.7.0. Please check and confirm the bug fix here.