Not too important, but for backup and for tinkering:
1) It would be good if all GraphicConverter support/config files would be in one place.
2) A consistent file naming scheme of the action files would be appreciated too. Currently some have a .gaction extensions, others don't have one, and I mean really they don't have it, not just hidden flag. I observed that those with .gaction are from 2022-04-16 or later. So this must have come with the changes for build 5480 which was shipped exactly that day.
[Added] Action files got .gaction file extension + Actions folder in container gets aliased in Application Support
[Added] Action files got .gaction file extension + Actions folder in container gets aliased in Application Support
Last edited by porg on Mon May 23, 2022 11:03 pm, edited 2 times in total.
- forum_adm
- Site Admin
- Posts: 1712
- Joined: Fri Dec 23, 2016 9:41 am
- Location: Germany
- Country: Germany
Re: GraphicConverter Actions folder is the only config folder in container and with inconsistent gaction file extensions
The new BETAs add always the action if you save a new action or rename it. So, the issue is solved for new actions.
Re: GraphicConverter Actions folder is the only config folder in container and with inconsistent gaction file extensions
Ad 2) Ok, I will add .gaction to the old ones to be uniform
Ad 1) Possible to put the Actions folder to the standard AppSupport folder?
Ad 1) Possible to put the Actions folder to the standard AppSupport folder?
- forum_adm
- Site Admin
- Posts: 1712
- Joined: Fri Dec 23, 2016 9:41 am
- Location: Germany
- Country: Germany
Re: GraphicConverter Actions folder is the only config folder in container and with inconsistent gaction file extensions
1) The GraphicConverter Finder extension requires access to the stored actions. So, it must be in this special folder due the Apple sandboxing restrictions for Finder extensions.
Re: GraphicConverter Actions folder is the only config folder in container and with inconsistent gaction file extensions
Understood. Knowing these circumstances, the best possible UX improvement would be:
When GC creates the Actions folder programmatically it could also create an alias to it in the ~/Library/Application Support/GraphicConverter/ folder, so that the average tinkering user has everything at least accessible in one place.
When GC creates the Actions folder programmatically it could also create an alias to it in the ~/Library/Application Support/GraphicConverter/ folder, so that the average tinkering user has everything at least accessible in one place.
- forum_adm
- Site Admin
- Posts: 1712
- Joined: Fri Dec 23, 2016 9:41 am
- Location: Germany
- Country: Germany
Re: GraphicConverter Actions folder is the only config folder in container and with inconsistent gaction file extensions
Thanks for your suggestion.
I add that link creation to build 5509.
I add that link creation to build 5509.
Re: GraphicConverter Actions folder is the only config folder in container and with inconsistent gaction file extensions
Will that link also be created for users already having a GC installation and/or the corresponding AppData (leftover) folder.
Or only when installing afresh?
Or only when installing afresh?
- forum_adm
- Site Admin
- Posts: 1712
- Joined: Fri Dec 23, 2016 9:41 am
- Location: Germany
- Country: Germany
Re: GraphicConverter Actions folder is the only config folder in container and with inconsistent gaction file extensions
That will created for all users if it does not exist (upon opening a browser).
Re: GraphicConverter Actions folder is the only config folder in container and with inconsistent gaction file extensions
Great! When the upgrade is available I will test and report here.
Re: GraphicConverter Actions folder is the only config folder in container and with inconsistent gaction file extensions
• In:
Code: Select all
~/Library/Application Support/GraphicConverter/
Code: Select all
~/Group Containers/FAVZJT8J4U.com.lemkesoft.graphicconverter11.group/Library/Application Support/GraphicConverter/Actions
• Opened a browser window in GC somewhere on my filesystem (regardless where)