#DEBUGGING PLUGINS IN AFFINITY PHOTO .EXE#
#DEBUGGING PLUGINS IN AFFINITY PHOTO CODE#
#DEBUGGING PLUGINS IN AFFINITY PHOTO WINDOWS#

As so frequently happens, I find that everything is far more complicated than I ever imagined. I wrote the following just to make things clearer to myself. Why it works this way is beyond my meager, end-user knowledge of Windows. Various users have reported these various approaches to configure Affinity 2 as an external editor in various other programs. While researching this problem and benefiting from the comments of many others, I learned the following, which may be of interest to others. It needs a feature to execute the App Execution Alias or to access the zero-byte.

#DEBUGGING PLUGINS IN AFFINITY PHOTO WINDOWS#

What Faststone and other applications need is a new or upgraded feature that enables calling Windows Apps from their hidden system folder. The function is merely incomplete under the new methods of installing Affinity 2. Faststone's external editor feature is working as designed in that it calls Affinity Photo from any normal location on the system. Under Affinity's definition, I think the fact that Faststone Image Viewer requires a work-around to launch APhoto2 is not a bug.

#DEBUGGING PLUGINS IN AFFINITY PHOTO CODE#

'We define a bug as something that isn't working the way the code intends it to.' Not to be too picky or pedantic, but I do think we require extreme precision in the use of words to avoid end-user B told me the other day that Hope this helps and apols if earlier lack of clarity has confused. anyway, I've done a couple of restarts and things seem to be working OK at the moment.Īs far as Walt's batch file is concerned - I can confirm it launches V2 from my desktop. I have no idea why my permissions changed overnight. I've now regiven myself permissions and am getting V2 to invoke via DXO and ACDsee but - I have now had a couple of requests to re-enter my licence/account details.

#DEBUGGING PLUGINS IN AFFINITY PHOTO .EXE#

exe in that folder - even though the desktop shortcut I'd created yesterday worked fine. Since I now know where the V2 app is I went to the folder to find I didn't have permissions that I had set up yesterday - so I think I couldn't start V2 by double clicking the. Or something like that - the upshot is I couldn't invoke V2 from DXO. When I came to explore V2 this morning I tried to invoke V2 from DXO but got a message along the lines of (sorry - I've been fiddling for a couple of hours so can't remember exactly) 'can't access'. I started this morning by starting from the desktop shortcut I'd created yesterday. And apologies but the precise order of what I've done is lost in the mist of exploration and button presses. I'm using DXO and ACDsee and, as far as I can see, I can only invoke.

This a follow up and a bit of clarification since my response to Walt has been picked up.įirstly clarification - I've not used Walt's batch file to invoke from a 3rd party application.

Debugging plugins in affinity photo