Raw Therapee leaves a directory behind in 'Documents and Settings\activeuser\Local Settings\Application Data'. Not sure when the directory is created. I found it after creating a processing profile that didn't move to a different computer. I currently do not have a virgin computer to determine when the directory is created.
Clair
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Is there some reason you didn't mention what directory is actually created? Also, can you state the exact steps you took to cause the directory to be created? You can delete or rename the existing one to figure out when it was created.
I wasn't able to reproduce this issue on Windows 7 (equivalent being C:\Users\Username\AppData\Local) even when opening files.
Sometimes, the impossible can become possible, if you're awesome!
This in on WinXP. I just ran it on a machine that I do not use to process raw photos. The full path is C:\Documents and Settings\UserName\Local Settings\Application Data\RawTherapee4.0.11 The directory is created on startup of Raw Therapee. No additional steps required. I only have WinXP so I cannot reproduce on other operating systems.
I can confirm this behaviour. However, on a clean Win7 VM, I'm getting a directory name of RawTherapee4.0.
Fortunately, it's easy to take care of in the next revision. For now, add this line to RawTherapeePortable\App\AppInfo\Launcher\RawTherapeePortable.ini, immediately after cache=%FullAppDir%\cache:
Also ensure there's a blank line following that one prior to the next section.
[EDIT] Note that you'll need to manually delete the current folder prior to running RawTherapee Portable after making this adjustment, or you'll be leaving the current one there afterwards.
Side note - I can also confirm this behaviour for Stellarium, which leaves LOCALAPPDATA\stellarium - which includes some cache folders inside it. I'm opening a seperate bug for that one.
That fixed it.
Clair
We have the workaround from Gord above, but still need to apply the fix to the actual app, so we'll keep this as a Bug until then.
Sometimes, the impossible can become possible, if you're awesome!
This is fixed in today's release.
Sometimes, the impossible can become possible, if you're awesome!