I'm quite confused on this.
From the release notes: Pairs built using regular expressions allow you to find and replace parts of one path to make the other. For example, if you have various "Production" and "Staging" folder hierarchies in different places, you can set up a single rule that lets you display *\Staging\* on one side if *\Production\* is on the other.
I tried to make a paired folder Using two new Folders named Test1 and Test2.
Under Test1 I made a subfolder named HelloA and under Test2 I made a subfolder named HelloB.
1: The release notes indicate Regular Expressions, but the documentation uses Wildcards.
2: Selecting the Match / Replace Option greys out the explicit path Primary Folder / Paired Folder option.
3: Is it possible to solve this simple paired folders problem ?
I have so far been unable to navigate my simple test structure using paired folders.
Yes fair point, although the release notes are really just a description of the feature rather than documentation on how to use it, which hasn't been written yet.
When you use regex mode you're not specifying a particular folder, which is why the folder fields are grayed out. You're specifying a pattern which will be tested against every folder you enter to see if it matches. If it matches, the replace expression produces a new string which becomes the pair.
As the "example" in the release notes suggests, regex mode is useful when you have folder trees that are all the same except for one or more components. Then you could use regex to test for the common elements, and replace the bit that needs to change. Your example has no components in common, so I wouldn't say regex is really suited to that.
Hi Leo, I have tried multiple variations of options selected, making sure Navigation Lock is active, but it doesn't seem to open the paired folder on the B lister. I also tried some more basic examples based of the documentation, and it doesn't open the paired folder either.
I am on the latest version on my personnal laptop. When running the test inside the configuration window, I get the right output, but that is not a proper in-situ test.
What does work however, is going into the single lister mode (F6), then opening Test-A, then going into the double lister mode (F6 again) - which opens Test-B.
In other words, I need to start from a single lister view to have Test-B open. The script executes when the view is changed.
