walt.farrell

Yes, that's what causes some of the issues, but note that even Mac users are told to turn off Metal or adjust something else in the rendering settings so that's not all of the problem.
In theory the benchmark code could run various tests and see if any crashed outright, or if in any of them the GPU/driver never returned control to the application. If either happens, that GPU/driver is not appropriate for using the hardware acceleration and that option should be turned off.
For users with multiple GPUs it could even test each of them individually and together. It does that to generate the benchmark numbers today.
To display sample images and ask whether they looked OK would be more work, of course, but is also theoretically possible.
And from that it could either provide a recommendation or simply set the options appropriately and say "recommeded settings now established".

If you're talking about the blue frame around the top text, that's probably View > Show Text Flow.

probably this one,from 2021 has a similar zooming included.

 
the magic starts at ~1.58Minutes in.

There's one much newer (and faster as I recall) than that. Within the last 3-4 years, I think.

Affinity has (or had, I'm not sure where to find it) a very similar video showing zooming in deeper and deeper into a design in Designer, too.

For others, or in case you're still missing the context:
 

Duh, sorry guys, it seems muh' brain's running on farts today... I had moved the linked image folder and the dimmed out button didn't register... I'll go ahead and delete this post @walt.farrell @Old Bruce

What commands?
What OS?

For others, or in case you're still missing the context:
 

I would then precise it in the name or description (even for other languages, as you did for English. In French, insécable=non-breaking and sécable=breaking) : 
em/en quad = breekbare em/en [+spatie if one wants] or Em/en spatie (breekbaar)
em/en space = onbreekbare em/en[+spatie] or Em/en spatie (onbreekbaar)
 
Since the difference is only the fact they are breakable or not, there was no point before computer composition to distinguish them: in older time, the decision to break or not was made by the typesetter operator.

Generally the resize step will do something, but will do it in a way you won't like. It would distort any image you apply it to that does not have the same aspect ratio as the image you used when recording the macro. And that probably is not what you want.
The usual recommendation for resizing images using macros is to use Filters > Distort > Equations which will not have that problem.
You can find more on doing that in the Resources section of the forums: https://forum.affinity.serif.com/index.php?/search/&q=macro resize&type=forums_topic&quick=1&nodes=11&search_and_or=and&sortby=relevancy
If your macro is truly doing nothing, I'm not sure what might be going on.
 

In the Data Merge Manager you can specify the separator you want to use:

 
But using LibreOffice Calc, I have no problem generating a CSV file whose fields contain the "," character, and which uses the ";" as the separator. And as mentioned above, any fields that contain a "," are automatically quoted. And the file works properly for Data Merge.
Samples (using Publisher 2.5.0.2402, but should open in Publisher 2.4):
data-merge-test.afpub Untitled 2.csv

From your description of them, though, em/en quad are not "non-breaking" like em/en space are, which would seem to give them a purpose: An em/en space if the surrounding characters are on the same line, but do not force them to be on the same line.
Or should their description be amended?

The applications are coded for specifications such as the OpenCL specifications, which are not provided by the OS but by an industry consortium.
The drivers and GPUs are also coded for those specifications.
Any of those (the application, or the drivers and/or GPUs) could be coded incorrectly. Sometimes it may be Affinity, but sometimes it is the drivers or GPUs that have the issue.
The Affinity applications will run without that requirement, as far as I know. And if the GPU/driver does not provide it, the settings will be disabled automatically by the application. The problem comes when the GPU/driver claims to provide OpenCL and Direct 3D level 12 support, but does not provide it completely or correctly or fully, then Affinity will enable it based on the GPU/driver's claims, and problems will result.
Both freezing and crashing can be due to errors in the GPU/drivers. It's not just display problems.
I have no idea what would be possible in this area, but it's an interesting idea.

Thanks @walt.farrell, I will study the link you have replied. All the other steps are working in my makro, except resizing. 

I don't think there's any way to invert a selection of layers directly.
With a single page PDF, you could Hide all the objects you currently have selected by Hiding one of them in the Layers panel. Then Select > Select All Layers, which will select everything that's not Hidden. Then Delete. Then select all the layers using the Layers panel, and unHide one of them.
 

But the chart includes both "em quad" and "em" and  "em spatië" is already used for "em".

In the Data Merge Manager you can specify the separator you want to use:

 
But using LibreOffice Calc, I have no problem generating a CSV file whose fields contain the "," character, and which uses the ";" as the separator. And as mentioned above, any fields that contain a "," are automatically quoted. And the file works properly for Data Merge.
Samples (using Publisher 2.5.0.2402, but should open in Publisher 2.4):
data-merge-test.afpub Untitled 2.csv

The descriptions are correct so you're right, there is one use case where you might use them.

You're right, now I see the conversion error too!

Thanks Walt (and RCR). Much appreciated.

I think my workflow is rather simple: I share a .dng (or other raw format) to affinity Photo on iPad to be able to process it in Affinity Photo. It gets opened in the Develop Persona etc.

When I save the file I choose to have it embedded in my .afphoto document. Seems quit straightforward to me.

I prefer to work in a wide gamut colour space, hence my choice for ROMM RGB.

Sometimes I want to go back to the Develop Persona while working on a file in order to change some basic settings. Not often, but it happens. That is why we can go back to this Persona, right?

I discovered this issue by accident, I was surprised by some colour differences between files from an older Adobe workflow and the ones I was seeing in Affinity. I noticed a difference in colour profile that I was not expecting etc.

Let me add something though:

When I changed the colour profile from sRGB to ROMM RGB I had some serious problems with the Selective Colour adjustments that I already made previously, I basically had to redo that.

I have a feeling that the default colour space setting is not stable in the iPad versions of the Affinity applications, they seem to change somehow back to the standard sRGB from time to time. I have no proof of that yet but I set a wide gamut colour profile as default but somehow they get changed back to a default sRGB, it seems. Not definite proof yet, though.


 

I don't think that's quite right, at least for Windows.
On Windows, the GPU and its drivers indicate their capabilities, and if they claim that they support the correct levels of processing and OpenCL, then Affinity Photo trusts that they are telling the truth and allows you to enable Hardware Acceleration.
Issues can arise when the GPU or drivers lie about having the proper support, or they have implemented the support incorrectly. (Or, I suppose, if Affinity Photo is using it incorrectly, but I'll ignore that as we have seen definite cases where it is the drivers that have the issues.)
I'm not sure to what extent that would be possible. If the error is one related to the on-screen display, such a test would require that the application be able to contain a copy of the expected screen display given a particular starting point and sequence of applications, and that it then be able to perform those operations and then retrieve, from the GPU, the current screen display to make a comparison. If that that retrieval is possible, then what you propose sounds like an interesting idea. 

I may not have understood what you want correctly but if you have selected the objects you want to keep, you can copy them to the clipboard & use File > New from clipboard, you will get a new document with just those objects in it on a canvas just large enough to enclose them all. Then if desired/necessary you could resize the canvas & export that to a new PDF.

With all the layers you want to keep selected, right-click one of the selected layers and select Lock

Select > Select All Layers will then just select the unlocked layers