![]() Registered Member ![]()
|
When I download and install the "Installer" version of Krita then all settings are stored (on Wondow) in the following directory:
C:\Users\M\AppData\Local Ok. But what if I download and install the "portable" version of krita? Then the settings must be stored somewhere INSIDE the Krita base folder. Where exactly? The full "share" subfolder? I want to copy them to the new version directory (when updating). Peter |
![]() KDE Developer ![]()
|
By default, the settings are stored in the same place. If you want them stored in another place, you need to create a batch file or something like that that sets various XDG environment variables: https://standards.freedesktop.org/based ... #variables
|
![]() Registered Member ![]()
|
Ok, I accept your answer. But then Krita "portable" version is not really portable. |
![]() Registered Member ![]()
|
Hello! I've tried to set various XDG variable on Windows 10 x64 with this batch
I've found that variable XDG_DATA_DIRS always sets internally by Krita and even if I change it and move the folder before launch XDG_DATA_DIRS always points to "C:/Krita/bin/../share" after launch I've tried various combinations of forward slash and back slash in paths... But still Krita stores it's setting under "%AppData%\krita" folder and "%LocalAppData%\kritarc" file and completely ignores preset XDG_DATA_HOME , XDG_CONFIG_HOME , XDG_CONFIG_DIRS , XDG_CACHE_HOME variables... Nothing appears under that folders, not even a temp file ![]() I'm using Krita v3.3.1 x64 portable, downloaded from official Krita site Am I doing something wrong? |
![]() Registered Member ![]()
|
There are at least two options for a portable version of Krita.
1. PortableApps.com has version 4.1.7 at https://portableapps.com/apps/graphics_pictures/krita-portable 2. The user should download the Windows Portable Krita (64-bit or 32-bit) Zip file, and extract to the portable drive. I have put together a batch file to run Krita. The batch file should be on the same drive as Krita, but does not have to be in the same folder. It makes portable two folders: AppData\Local and AppData\Roaming\Krita. The configuration file kritarc has at least one setting that should be changed. The easiest way is from the Settings menu within Krita, the first time it is run. Configure Krita > G'Mic-Qt Integration will show a location, such as H:/krita-x64-4.1.7/bin/gmic_krita_qt.exe. Drive letter assignments can change for removable drives. The user should delete the explicit drive assignment. In this case, delete H: . Also, Krita defaults to putting a swap file on the system drive (usually C:) in AppData/Local/Temp. If the user wishes, that file’s location can be changed to the removable drive with Configure Krita > Performance. There is a forum topic about security and performance: Krita FAQ About Slow Start-Up in Windows Here is the batch file:
____________________________________ Update for version 5 G’Mic is now included into Krita itself, and thus does not need to be configured separately anymore. The Resources tab has been added to Configure Krita > General. It is used for setting the location of the Cache and Resource folders. They default to the system drive (usually C:) as shown here: C:/Users/user name/AppData/Roaming/krita Drive letter assignments can change for removable drives. The user should delete the explicit drive assignment. In this case, delete C: . Also, these folders can be placed within the program folder, or elsewhere if the user wants a greater separation between the folders and the program. The following examples illustrate these two approaches: /krita-x64-5.0.0/AppData/Roaming/krita // within the program folder /AppData/Roaming/krita // separate from the program The note above concerning the swap file location still applies for version 5. Configure Krita can set the location for the Cache, Resource, and swap file folders. They can also be set by editing these entries in kritarc, which is a plain-text file: ResourceCacheDbDirectory= ResourceDirectory= swaplocation= |
Registered users: Baidu [Spider], Bing [Bot], Google [Bot]