Added the following codes:

• Date

  • %DATE_YEAR%
  • %DATE_MONTH%
  • %DATE_DAY%
  • %DATE_ISO% [ISO 8601, in the form of yyyy-MM-dd]

• Time

  • %TIME_HOUR%
  • %TIME_24HOUR%
  • %TIME_MINUTES%
  • %TIME_SECONDS%
  • %TIME_AmPm%

• System

  • %SYSTEM_USER%
  • %SYSTEM_MACHINE%
  • %SYSTEM_DOMAIN%

Will add more when I (or someone else!) come up with 'em...

Hold on a sec - the Multiple Destinations feature will also need to support these codes. Oops. Erm, okay; should probably display the codes within that form, too.

Added a DestinationCreationMode option to the Settings - Advanced section. It's set to Auto, which won't prompt you to create the destination directory if it doesn't exist as that can get annoying if you're using %codes% within said destination.

Actually, removed DestinationCreationMode and any pop-ups about the destination not existing. FileSieve will now always automatically create the destination directory location if it doesn't exist. Probably should've done that from the start, really.

Changed codes to be their .NET Date format string equivalents; probably not as easy to use for beginners, but it reduces the huge number of characters required to represent something simple like a date.

For example:

%DATE_YEAR%

is now

%yyyy%

It also means many more codes can be added without having to come up with contorted names. Having %DATE_YEAR% equalled 2020, but what about the last t two digits of the year? %DATE_YR% - kinda rubbish.

Added loads more codes/tokens.

It appears I started on a DateTime formatting editor (see the Extras menu within FileSieve)... no wonder it all felt like deja vu.

Added Source Item %codes%. Consequently, the Explore Root Destination button to the right of the destination (to open it in Windows explorer, DOpus, or whatever file manager is the system's default) will now try to open the specified destination; if it can't, it'll then remove the trailing directory and try to open that. It'll keep doing that until it either manages to explore a directory or it runs out of paths.

This is because you may now have a Root Destination that looks like Z:\MyFolder\%siname% where the %siname% portion may not exist (it's the name of the currently-processing Source Item) and so FileSieve will attempt to then open Z:\MyFolder instead. If that doesn't exist, then it'll attempt Z:\; if that also fails, you'll get a message about it.

All references to %siname% have been changed to %folder%.