v_kyr

Well, UI component wise I would always name it as the dev systems on a specific host system (Windows or MacOS) names those GUI components. In case of Windows systems VS predefined UI-components this is more a ComboBox UI-component than a by MS so called Menu Strip. - But in CS & Java I can easily make an own UI-component out of a free placeable Dropdown Menu which looks and behaves the same. The Win VS way ... 2023-02-06_01-52-56.mp4 However as already said, if own GUI components are used and not the predefined VS Win ones, such a ComboBox can also be done via a Dropdown Menu (even with the down arrow pointer), so it always depends here what GUI components libs (or own custom defined components) have been internally used! - Thus I would say both answers are to 50:50 correct here, since it can be done with either of those UI-components.

I'm actually not on the Mac computer, but I highly doubt that El Capitan supports ProRAW here. https://support.apple.com/en-us/HT211965 https://discussions.apple.com/docs/DOC-250006566

Can't tell my MacOS and Photos versions are so old (pretty outdated), I also don't/can't run V2 apps on the old system. - On my old Photos version I have to export RAW files first in order to make any use out of those in other third party apps.

No sorry it's Ok, I've looked previously over a wrong covered browser win. - It's all well here!

AFAI recall it had been already said in the forum that "Edit With" is broken in actual MacOS versions due to Apple changes.

Wrong forum section for such Q's! However, look at this online help here which tells down the page bottom, slightly more about the dash line style. - And yes, the docu is pretty vague here, could be better and needs to be reworked!

Then the OP should be able to open them right out of the box. From APh try from the main menu just "File -> Open ..." here!

The OP can check via LibRaw, which tells the same here!

See ... The iPhone 13 pro max is not among the list!

Well most of those benchmarks are just of synthetical nature (CPU/GPU limited) and thus don't tell much about a wholes system behavior under more daily application working and/or stress conditions. Thus real application benchmarks are in contrast here often overall much more meaningful than synthetical ones. For application benchmarks the BAPCO suites are useful, but not all of them are crossplatform usable here. In order to check against the PC & Mac platforms here a cross benchmark (crossmark) would have to be used then.

All those Adobe, C1, DxO ... do check cams, lenses etc. on their own and have specialized teams for this of course in a much more professional way. They also don't rely on free opensource volunteering people and software ( like LibRaw, Lensfun etc.) therefor. Also they come pretty close(r) to what the cam vendors (who of course finally know their cam equippment and internal software best) themself do offer here. - IMO one can't really compare APh's development persona to pro RAW converter software like C1 or Lightroom, there are of course differences like day & night between these here. Darktable, well have some longer time not looking after that one, same as for RAWTherapee (which is good for workings in LAB mode), or DigiKam and the like. - As a Nikonian I personally use for RAW processing mostly Capture NX/Nikon Studio, C1 and partly DxO, since these do give me personally the best image results. - In the past I've used Lightroom and Aperture too but abondoned those years before. I don't use APh for RAW processing, just for other image manipulations and tweakings.

See also ... Bookbinder JS GitHub Bookbinder-JS ... etc.

Export settings PDF export For printing, print that PDF then, or hide/disable all layers you don't want to print from a document.

Sure should do basically the same, but what if the respective Affinity app cores before performing that operation, or doesn't start that CLI cmd way at all here for you? - My OpenCL Disabler tool isn't dependent on a running Affinity app at all, it works completely independent and doesn't need an Affinity app to run at all.

My point is/was more that they named that PROFILES which aren't ICC-/ICM-Profiles but instead just specific coloring presets, aimed after those the specific cam vendors use internally as optionals. - So what Adobe calls/named here Profiles are more specific Presets for me (Nikon for example calls them Picture Controls). -- So "Color Profile = Color Presets" here. Yes, you are not forced to take those out of the EXIF data, you can apply them anytime via the software afterwards too, even if they have not be setup in the cam during image capturing. Since then they're just going to simulate those on demand (...what some third party RAW tools offer and support to do). - But in order to know if one and which one was in cam setup during image capturing session, you have to read it out from the image EXIF settings here. - That's the point I meant! Only the better RAW converters (CaptureOne, Lightroom, DxO ...) do offer this functionality since you have to know all camera vendors cams and systems well therefor in order to simulate this in the same way as the venfors do in cam and with their own software. - Affinity's RAW converter is (as many other opensource ones too) based on the free LibRaw here, which AFAIK doesn't support and take that into account.