In Portable Mode LogExpert Tries to Save Persistence File to Log File Location (instead of Application Startup Directory)

[EnigmaSolved]

Greetings! I'm trying out 1.0.0 RC1 on Windows 11 Pro, and using it with Portable Mode Activated. Automatically save persistence files is checked, and Persistence file location is set to Application Startup Directory.

The logs I am viewing are from a Read-Only directory, and so I keep getting the error Unexpected error while saving persistence: Access to the path __________ is denied. because LogExpert seems to still be trying to save persistence files there.

Since I'm using it in Portable Mode (and planning to have it on portable storage like Google Drive so I can use it across multiple computers) I'd like persistence files to just be within the application folder somewhere. I thought from the docs that is how it would work, but maybe I am missing something (which is entirely possible 😆)?

A totally unrelated thing (if you'll pardon my tacking a separate question on here): I'm trying to understand the syntax for the MultiFile File Name Pattern. The default is *$J(.), and I gather that * is a standard wildard, and $J is for file index number, but I don't quite follow what the (.) portion does?

Some of my logs are in the format of: name.log.0 and then older ones are name.log.1, name.log.2 and so on, where the lowest number (ie, 0 is the most current). What syntax should I use to recognize these?

Thanks in advance for your assistance!

[Hirogen]

Should be possible, see settings

[Hirogen]

when I use this, configured like this, all my lxp files are saved in the "My Documents\LogExpert"

[Hirogen]

Pattern: *$J(.)
Matches file names like:
• logfile (no index, no separator)
• logfile.1 (index 1 with separator)
• logfile.2 (index 2 with separator)
• logfile.123 (index 123 with separator)

$J: Optional index (0 or more digits)
(.): Conditional separator (shown only when index > 0)
Use case: Matching files like app.log, app.log.1, app.log.2 where the base file has no number

so its probably no recognizing your files because they start with a 0