FastRawViewer now supports APh

[RichardMH]

FastRawViewer's latest beta supports Photo as a plug in.

https://www.fastrawviewer.com/blog/FastRawViewer-2-0-6-Beta

 External editors: it is possible to use macro tokens which will be expanded into system-specific paths.

Targeted to ease Affinity Photo 2 support under Windows, use

%localappdata%\Microsoft\WindowsApps\AffinityPhoto2.exe

to run Affinity Photo2 as an External Editor.

[Pšenda]

 

[RichardMH]

What he's done is set up a macro to make that easier

Supported macros (case insensitive):

• %localappdata% - local settings folder. Expands to
  • Windows: C:\Users\[Windows username]\AppData\Local
  • macOS: ~/Library/Preferences

[walt.farrell]

He has done more than that, because browsing to the full path in 2.0.5 doesn't work. When you get there, it tells you that the file is not accessible.

And browsing to the full path also fails in the 2.0.6 beta. He is recognizing %localappdata% as a trigger for some different processing.

[Iliah Borg]

On 11/20/2022 at 4:09 PM, walt.farrell said:

He has done more than that, because browsing to the full path in 2.0.5 doesn't work. When you get there, it tells you that the file is not accessible.

And browsing to the full path also fails in the 2.0.6 beta. He is recognizing %localappdata% as a trigger for some different processing.

Browsing won't work because the user has no 'read' rights, only 'execute' rights.

[walt.farrell]

30 minutes ago, Iliah Borg said:

Browsing won't work because the user has no 'read' rights, only 'execute' rights.

It will work, but only if you use the form of the path using %localappdata% and not the actual expanded path name.

[Iliah Borg]

8 hours ago, walt.farrell said:

It will work, but only if you use the form of the path using %localappdata% and not the actual expanded path name.

I was explaining why "browsing to the full path also fails in the 2.0.6 beta".

[walt.farrell]

47 minutes ago, Iliah Borg said:

I was explaining why "browsing to the full path also fails in the 2.0.6 beta".

Thanks, I didn't understand that.

It seems to me, though, that since it can be invoked when %localappdata% is used, it could be invoked using the full path. Better, though, would be to just let the user enter the executable name, and depend on Path being set appropriately.