fde101

Panasonic LUMIX DC-S5 Panasonic LUMIX DC-S5M2 Also, I just downloaded a random sample RAW file from the S5 II camera from the web and verified that I can open it in quick view in the finder and in Affinity Photo 2 when it is set to use Apple's RAW engine (it does NOT open correctly when set to use the Serif RAW engine).

They may be pointing to a version for an older macOS: https://support.apple.com/en-us/HT213267

If you are on a current version of macOS, you can use the Apple RAW engine instead of the Serif one, and then it is supported. For the Serif RAW engine used in Windows versions of the Affinity products (and as an alternative to the Apple engine in macOS) it generally follows the releases of libraw, so you are better off checking on the release schedules for that project than asking here: https://www.libraw.org/node/2753

This part of the forum is primarily for feature requests. Bug reports go here: https://forum.affinity.serif.com/index.php?/forum/71-bug-reporting/ These are actually three separate reports and should be split up. I suggest searching to make sure those first two were not already reported, then move them to the bug report section and remove them from the first post here. That third item does appear to be a feature request / improvement suggestion so this is the right place for that one.

It is also used for any pixel layers you create, and for rasterizing elements using the relevant commands (such as Rasterize & Trim, etc.) If you set the rulers to use pixels as your design unit, the DPI comes into play for mapping between pixels and inches/centimeters/whatevers. There are many ways in which that setting is used in the Affinity products, and enumerating them within that dialog box is probably not the most effective use of that space. A link from there to a help topic would likely be more appropriate if anything.

Not sure that I follow why this is a problem? The whole point of the baseline grid is to keep even spacing of the lines of text by aligning them to the grid. This is not a generic layout grid - its entire function is to keep text evenly spaced. Why is it a bad default for the grid to be used for the very thing it is intended to be used for? If you want a generic grid to line up shapes against and such use View -> Grid and Axis to set that up.

Suggestion: add a button to the dialog that rasterizes the resulting shape to the selected or topmost pixel layer instead of creating it as a vector shape (it could create the pixel layer when there is none). This may be a useful shortcut under certain conditions.

I don't see it in the list of keyboard shortcuts which can be customized, so thinking it may rather be a missing feature. Either way it would be good to have those added.

In theory, the page up/page down keys should scroll by a screenful, while the versions with the shortcuts should switch pages. The screenful scrolling fails to work in the Affinity apps, however.

The whole point of the namespace system is to allow for arbitrary 3rd-party extensibility, so Serif appears to be using this correctly. I don't believe there is an error here. The problem is that the validators cannot find the DTD and thus cannot validate that the usage of the Serif namespace matches its intended usage. The correct way to solve this would be for Serif to make a DTD for their namespace available for use by validators, not to eliminate it completely.

I haven't tested how this impacts that particular export format, but have you tried dragging from the corner of the rulers to the point you want to use as the origin? That does at least adjust the origin point within the app itself...

As a workaround, you could try duplicating the shape that you want to export from and use it as a mask for the parchment, then export the selection area. The mask can be turned on and off so that you would only enable the mask when you want to perform that particular export.

For text styles you can already do this: right-click the style in the Text Styles panel and choose the option to Edit the style. There is a field for a "Keyboard shortcut:" on the "Style" page of the resulting edit window. Frame text is meant to contain paragraphs of text. It creates a text frame which is already prepared to receive text and which you can use immediately, covering the most common use case without requiring extra steps. Placing an empty text frame on a master page gives you a placeholder for entry of page-specific text on pages which include that master. Artistic text is text that can be warped, put on a path, etc. - text that is "loose" within the page as opposed to containing entire paragraphs. It gives more creative control for special decorative use cases. Uniquely, this cannot be used empty as a "placeholder" on a master page. The shape tools create an assortment of shapes which are not initially prepared to contain text. You can convert them to text frames in order to add text to them, but this is an extra step. Placing a shape on a master page without explicitly converting it to a text frame does not give you a placeholder for entering text. The image frame tools are not meant to contain text, but rather pictures. These are used on master pages, for example, to create placeholders where images can go. File -> Document Setup and on the Model tab in the resulting window turn off Facing pages.

This would be better handled by adding support for stroke offsets to the Appearance panel and allowing a choice of strokes, fills or both from the panel to be saved as partial styles which can be applied to arbitrary objects from a palette, replacing only those parts of the appearance which match what was saved to the partial style.

I believe it is rather obvious that the OP is asking for the "global layers" feature that has previously been discussed at length in other threads (making this one redundant). The lack of this feature seems to me like one of the most blatantly obvious major shortcomings of Publisher in particular.

MSI vs MSIX? Were they installed under different user accounts? Are the users who do not have the option enabled local administrators?

Not sure to be honest as I've never actually saved anything with a duplicated RAW layer or paid attention to that. I did test that procedure to the point of it working but for any actual work on RAW images I use a dedicated RAW processor (Capture One, DxO PhotoLab, etc.) to handle the RAW development then round-trip a PSD from the RAW processor into Affinity Photo when I need to perform edits I can't do as well or at all in the RAW developer. While I am sure Serif would not present it this way I tend to think of the Develop persona as a concession to people who don't have "real" RAW development software to work with... the dedicated software that is out there will generally be faster to work with and give better results.

They do show up in the menus in the menu bar, so yes, the shortcuts are there and do work (except they are Command+X, Command+C, etc. rather than Control), it is only the context menus that do not display them.

Platform convention. Context menus do not show shortcut keys.

Please search before posting new threads which are simply duplicates of existing ones. In particular, there is a pinned topic "Scripting" at the top of the forum where Serif has already announced that they are working on this. It is not anywhere near ready for release yet, but it is underway. It is best to keep discussion on one topic in one place, rather than scatter it across numerous threads.

If you click within the area of the text frame it will simply move the insertion point, and if you click on another text frame it will simply switch to editing that. If the shape extends beyond the edges of the text frame you should be able to click within the shape but outside the text frame to select the shape. Even better, don't bother creating a text frame for this: right-click on the callout shape and choose Convert to Text Frame. This will make the callout shape and the text frame one and the same so there is no need to change the selection.

If all you are trying to do is switch layers/objects you don't need to switch tools to do that. Even with the text tools selected you can simply click on another layer to switch. Doing so also takes you out of text editing mode if the layer you click on is not another text object so you could then switch tools directly to whatever you need to use.

Yes, the "iPadification" effect - it changed from Preferences to Settings in macOS 13 (Ventura) throughout practically the entire system, with even most applications changing their "Preferences" menu option to a "Settings" one, but some older apps may not adapt unless/until their authors update them. Some apps are too bone-headed to adapt to platform conventions regardless and will probably always say "Preferences" or "Setup" or whatever they chose to use for that app; apps with completely custom interfaces such as Blender generally fall into this category. The Affinity apps are kind of half and half on this, but they do say Settings under macOS 13 in any case.

This already seems to work as the guides already appear when moving the artboards. The guides being requested seem to be more for comparison/analysis purposes, and that is where I am a bit lost, as they export largely independently of each other, so I'm not sure what the benefit of that would be.