Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Trouble with addonCollectionManager
#11
(6 hours ago)rich2005 Wrote:
Quote:  default folders, appended to \Users. But I avoid them like the plague....

I suspected someting like that. (your are talking to the (linux) converted where I have much installed and running from a storage partition).
AFAIK unless you use a portable Gimp you will get a C:\Users\"yourname"\AppData\Roaming\GIMP\2.10\ set of files and folders. What does Edit -> Preferences -> Folders show Did you maybe delete the default path(s)

The plugin just copies then deletes to that location.

With Gimp 2.10.22 installed on a Drive F: I can get it working with (just the beginning of the ini file) and the files stored in sub-folders (xxx_resource) under a main folder  F:\resource\

Code:
#-------------------------------------------------------------------------
[all]
# enable:brushes dynamics fonts gradients palettes patterns scripts
enable:brushes fonts patterns scripts
addons_active:{GimpUser}/{type}
addons_stored:F:/resource/{type}_storage
menu_location:{<type>}
menu_entry:{type} sets...
menu_description:Manage {type} sets...
dialog_title:{type} sets manager
[brushes]
menu_location:<Image>/Resource
extensions:.gbr  .vbr  .gih  .abr  .GBR  .VBR  .GIH

Ofnuts might have some solution, possibly starting Gimp from a batch file where new Gimp environmental variables are set.

You just need to set the environment variable GIMP2_DIRECTORY to point to the directory that should hold your profile. Can be done in a .BAT, but you can also set that variable system-wide, so that all Gimp invokations see it. If you use a .BAT you have to assign it as the opening application for several file types, while the environment variable technique will work with your current file associations.
Reply
#12
(6 hours ago)rich2005 Wrote:
Quote:... You just need to set the environment variable GIMP2_DIRECTORY to point to the directory that should hold your profile. Can be done in a .BAT, but you can also set that variable system-wide, so that all Gimp invokations see it. If you use a .BAT you have to assign it as the opening application for several file types, while the environment variable technique will work with your current file associations.
Thanks! Plugin now working--though I had to migrate the configuration files. Tanks again.
New: my elation, premature. Plugin worked on first run--but
Big Trouble: Gimp took control of E:\GimpResources, and all {type}_storage folders containig subdirectories got deleted--contents of subdirectories moved to {type}. So, undoing changes.
Reply


Forum Jump: