Patrick Connor

Frames are not "Affinity Resources", in the same way as computer screens are not Resources for displaying images exported from Affinity Photo or Designer. 
Yup

Affected is just the ms-appinstaller URI (Uniform Resource Identifier) scheme (protocol), and that URI scheme should as default either way be disabled. It was used in the pasts for an app installation directly from a web server (so a web page, see therefor also), before it has been misused by some cyber criminal elements.
The overall reason therefor Microsoft did so, is closing a possible security hole of misusing the Web App Installer by financially motivited threat actors.  

Frames are not "Affinity Resources", in the same way as computer screens are not Resources for displaying images exported from Affinity Photo or Designer. 
Yup

I think you have misunderstood the problem which lies with a particular protocol 
ms-appinstaller:?source=xxx
Which is included in some websites to distribute MSIX files. Serif don't use that protocol on our website.
This protocol has been stopped in the past also, see here
The MSIX installers themselves and the patching process are unaffected.

Frames are not "Affinity Resources", in the same way as computer screens are not Resources for displaying images exported from Affinity Photo or Designer. 
Yup

What I am reading is that Microsoft disabled the protocol handler that allows direct installation via a web URI.  This does not stop users from manually downloading an MSIX file and installing it.
I don't know if this will have an effect on the current Update process, but I will try that later when I'm at my computer.

This one was covered in table tennis bat rubber and the text on the top plate was also red.

Perhaps you should have made & offered instead some specific reusable Affinity framing template files here (so that this posting fits better into this forum section at all). Though on the other side for such trivial A4 prints to be framed, that's either way a nobrainer everyone can do on it's own.

Do you think I have nothing better to do than be here on Boxing day 😅

Do you think I have nothing better to do than be here on Boxing day 😅

Do you think I have nothing better to do than be here on Boxing day 😅

If you are a new arrival to this thread and have found that it is locked but still want to show your support for Affinity on Linux, simply like this post

I also checked V1, and V2 (2.2.1), and V2.3. The bug only occurs in V2.3.

Already known to staff:
 

Hi, I am Jan from Czech Republic. I am working for more than 20 years in advertising studio using Adobe soft for all that time. As their pricing politics after CS6 became unacceptable for me, I am still working with CS6 and because of it I have stuck on Mac OS Sierra. I have been thrilled when I heard about Serif's developing a serious alternative also to InDesign (Publisher). And I have bought Affinity V1 as well as V2. Unfortunately Affinity V2 don't support such old Mac OS version I am still forced to run on, so I am unable to run Affinity V2 simultaneously with Adobe CS6 to have good conditions for comparing and testing both apps to get know if Affinity (mainly Publisher) is on such level allowing me to leave Adobe (mainly InDesign). I had to install another HDD with Win10 where I can make my tryouts and tests in Affinity V2. From several testing works I have discovered, that full transition is still too "risky" for me (and partial transition is impossible due to OS incompatibility). However I deeply hope, that moment of my complete transition to Affinity is getting near.
I wish Serif team good luck in developing such difficult piece of software (as Affinity apps are) and looking forward to the day I will start use it for serious work.

You have installed a sandboxed version of Affinity Photo via an MSIX installer. Microsoft obfuscate the installed sandboxed MSIX software in a non-visible folder, so pointing directly to the real Photo.exe file is harder.
AffinityPhoto2.exe in your first post is Microsoft's' own solution to how to access sandboxed software executable. If you install the non sandboxed version instead (as suggested above) you can point your screen capture software at that instead. The contents of the sandboxed MSIX installer is EXACTLY the same as the contents of the MIS/EXE installer (which gives you a non-sandboxed version instead, with a findable Photo.exe). If you trust one you should trust the other.

It seems Photo curves adjustment is broken.
when selecting the alpha channel, no nodes are present at 0/0 or 1/1, and you cannot add any nodes manually to modify the curve.
choosing other RGB channels works.
 
 

Hi @NotMyFault,
Good find, I've replicated and logged this bug with the developers.
 

Le 29 septembre 2023 dernier, Steven Wilson a sorti son 7ème album solo : une merveille (selon mes oreilles et ce qui se trouve entre elles deux) pour ce musicien ultra complet (écriture, interprétation et production) et très productif, en plus d'être très créatif.
Voici une interprétation de la couverture de l'album sous forme d'un wallpaper en HD (5120x2880) et ma petite “sculpture” !...
Le 29 septembre 2023 dernier, Steven Wilson a sorti son 7ème album solo : une merveille (selon mes oreilles) pour ce musicien ultra complet (écriture, interprétation et production) et très productif, en plus d'être très créatif.
Voici une interprétation de la couverture de l'album sous forme d'un wallpaper en HD (5120x2880) et ma petite “sculpture” !...

 

Adding a new cover: Stevie Wonder - Songs in the Key of Life - 1976

We are pleased to announce Affinity Designer 2, Affinity Photo 2 and Affinity Publisher 2 are now all updated to version 2.3.0 (for all existing customers on all platforms).
Here are links to the release notes
Affinity Designer 2.3.0 for Windows               ( Microsoft Store and Affinity Store [as sandboxed MSIX and unsandboxed MSI/EXE] ) Affinity Designer 2.3.0 for macOS                  ( Mac App Store and Affinity Store ) Affinity Designer 2.3.0 for iOS                        ( Apple iPad Store )
  Affinity Photo 2.3.0 for Windows                    ( Microsoft Store and Affinity Store [as sandboxed MSIX and unsandboxed MSI/EXE] ) Affinity Photo 2.3.0 for macOS                       ( Mac App Store and Affinity Store )  Affinity Photo 2.3.0 for iOS                             ( Apple iPad Store ) 
  Affinity Publisher 2.3.0 for Windows              ( Microsoft Store and Affinity Store [as sandboxed MSIX and unsandboxed MSI/EXE] ) Affinity Publisher 2.3.0 for macOS                 ( Mac App Store and Affinity Store ) Affinity Publisher 2.3.0 for iOS                       ( Apple iPad Store )  Please follow this thread here to get notified when any new releases are made.

We were considering starting a 2.4 beta yesterday, but we have decided to add & test a few more changes before we start, so it will be in the new year but contain more.
I can see why you might think that but the Serif info bot post quoted above is actually suggesting that the localisation/translations will not be included in for new features and fixes until later in the beta and we did not want you saying that the feature was still in English when the beta started. The fix is that Find and replace field names are now capable of localisation. It was not actually not hinting at the beta start date at all 😜

We were considering starting a 2.4 beta yesterday, but we have decided to add & test a few more changes before we start, so it will be in the new year but contain more.
I can see why you might think that but the Serif info bot post quoted above is actually suggesting that the localisation/translations will not be included in for new features and fixes until later in the beta and we did not want you saying that the feature was still in English when the beta started. The fix is that Find and replace field names are now capable of localisation. It was not actually not hinting at the beta start date at all 😜

We were considering starting a 2.4 beta yesterday, but we have decided to add & test a few more changes before we start, so it will be in the new year but contain more.
I can see why you might think that but the Serif info bot post quoted above is actually suggesting that the localisation/translations will not be included in for new features and fixes until later in the beta and we did not want you saying that the feature was still in English when the beta started. The fix is that Find and replace field names are now capable of localisation. It was not actually not hinting at the beta start date at all 😜

We were considering starting a 2.4 beta yesterday, but we have decided to add & test a few more changes before we start, so it will be in the new year but contain more.
I can see why you might think that but the Serif info bot post quoted above is actually suggesting that the localisation/translations will not be included in for new features and fixes until later in the beta and we did not want you saying that the feature was still in English when the beta started. The fix is that Find and replace field names are now capable of localisation. It was not actually not hinting at the beta start date at all 😜