Page 1 of 2

[Added] Action files got .gaction file extension + Actions folder in container gets aliased in Application Support

Posted: Fri Apr 29, 2022 11:02 pm
by porg
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.


GraphicConverter Actions folder is the only config folder in container and with inconsistent gaction file extensions.png
GraphicConverter Actions folder is the only config folder in container and with inconsistent gaction file extensions.png (339.64 KiB) Viewed 1414 times

Re: GraphicConverter Actions folder is the only config folder in container and with inconsistent gaction file extensions

Posted: Fri Apr 29, 2022 11:05 pm
by forum_adm
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

Posted: Fri Apr 29, 2022 11:09 pm
by porg
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?

Re: GraphicConverter Actions folder is the only config folder in container and with inconsistent gaction file extensions

Posted: Mon May 02, 2022 12:54 pm
by forum_adm
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

Posted: Tue May 17, 2022 10:40 pm
by porg
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.

Re: GraphicConverter Actions folder is the only config folder in container and with inconsistent gaction file extensions

Posted: Wed May 18, 2022 9:41 am
by forum_adm
Thanks for your suggestion.

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

Posted: Wed May 18, 2022 10:33 am
by porg
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?

Re: GraphicConverter Actions folder is the only config folder in container and with inconsistent gaction file extensions

Posted: Wed May 18, 2022 2:07 pm
by forum_adm
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

Posted: Wed May 18, 2022 2:43 pm
by porg
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

Posted: Mon May 23, 2022 11:01 pm
by porg
✅ Closing issue - Now works as expected
• In:

Code: Select all

~/Library/Application Support/GraphicConverter/
I deleted my manually created alias entitled "Actions Alias" which pointed to:

Code: Select all

~/Group Containers/FAVZJT8J4U.com.lemkesoft.graphicconverter11.group/Library/Application Support/GraphicConverter/Actions
• Upgraded to GC 11.6.1 (5512) and relaunched it 👉 No alias got created automatically.
• Opened a browser window in GC somewhere on my filesystem (regardless where) 👉 The alias "Actions" in AppSupport got created automatically which points to its counterpart within the Group Containers correctly.