Prioritise Path Formats

I make extensive use of background images tied to wildcard Path Formats to visually identify folders. Sometimes there is more than one match. Is there a way of prioritising wildcard Path Formats as a means of forcing one matching format to be preferred to another. By default, whichever match appears latest in the list is applied. For example, if I have a path like this..

C:\Users\SomeUser\AppData\Roaming\GPSoftware\Directory Opus

and wildcard Path Formats like this...

\GPSoft
\SomeUser

The "SomeUser" format will override the "GPSoft" format by default. Is there a way to force "GPSoft" to take priority? The list of available formats does not appear to be manually sortable, so I suspect not.

Regards, AB

Wildcard formats are sorted (internally) by the number of components - wildcard paths with more components are tested before those with fewer (so that more specific patterns are matched before more general ones).

So you could change your GPSoft format path to *\GPSoft, which would make it more specific and therefore would override the SomeUser format.

Excellent. A neat and simple solution. Thanks Jon.

Regards, AB

I would like to apply specific backgrounds to selected project folders and a generic default background to all other project folders which could be anywhere on disk - i.e. not well suited to Path Format formats, but ideally suited to Wildcard Path formats. Is there a way of doing this?

In a structure like this..

[ul][li]Project-Alpha[/li]
[li]Project-Lambda[/li]
[li]Project-Omega[/li]
[li]Project-Theta[/li]
[li]Project-etc.[/li][/ul]
..combined with wildcard path formats..

[ul][li](Project-Alpha)(*|)[/li]
[li]
(Project-Omega)(*|)[/li]
[li](Project-)(*|)[/li][/ul]
Project-Alpha and Project-Omega specific formats are always trumped by the generic Project-*.
I expect this is driven by sort order - * coming before A(lpha). Is there a way around this?

Regards, AB

If the Project folders aren't directly below the root of their drive(s) then you could cheat and add an extra *\ to the front of the more specific wildcards and leave it off the generic one, to take advantage of that rule.

Failing that, another method would be to make the generic rule use a regular expression which uses a negative assertion to exclude the other folders. This seems to work, where b[/b] is the negative assertion:

\Project-(?!(Alpha|Lambda|Omega|Theta))[^\]+(\|$)

The folders in question are typically under the user's Documents structure so that is a good workaround. Thanks for the suggestion.

Regards, Ab