Portable version still using the appdata folder

[zzzzzig]

To be fully portable, Allusion shouldn't use the appdata folder. This would mean your database and settings are left behind when running from an external drive and changing computers. Most portable programs have the option to store their relevant data in the program directory, next to the exe. A few of them activate this mode by checking for the presence of a file called "portable mode" or similar next to the exe, and if it's not there defaulting to the standard appdata locations. This is to prevent dumping stuff to the appdata folders on first run, before portable mode is toggled.

As an added feature to make portable mode better, support for relative paths is always welcome. This would allow Allusion to access libraries on the same drive regardless of what drive letter happens to be assigned to said drive.

[cptvincer]

I second that. It would also help with any limitations someone might find with performance or amount of files/folders (as it would also allow to have different exes targeting different folders). Thats how Eagle does it and ive been using eagle with multiple libraries by type (and in different hard drives), like having stock photos and assets in one, drawing references in another...

I wish i could jump to allusion fully to replace most of my usecases with eagle since it reads directly from folders (and the way eagle handles files makes it a hurdle for me and use with some apps), and the way all folders are checked on load in allusion have limitations - fully portable Allusion, each with its own data would solve it beuatifully

[AlanDrake]

Plus one. Also please don't unpack the whole app into the appdata temp folder, it's not nice for SSD. If it needs to be unpacked, I'd rather a zip at this point.