fde101

If it is a requirement for you, this should have been verified BEFORE you blew money on the software. It is not safe to assume much of anything when it comes to what any particular software application will support, particularly with an edge-case format like DDS. You might think of it as some kind of standard because it is common in your own corner of the world, but for most of us its existence doesn't exactly have much in the way of mind share.

Why would you need decimal place accuracy for those color values?

Not even close:

That is what I intended to be covered by my fourth bullet point, not opening the popup at all, but simply dragging the color well onto the desired color to capture it directly into the color well.

I am thinking there are four things that should ideally happen here: Fix the color sampler to remember the captured color between uses. The fact that it keeps resetting might be a bug? It is not a useful behavior in any case. Note that mine resets to the color that is set in the color well rather than always to red, but in any case, it is not retaining the captured value. Have the color sampler automatically apply the captured color when a modifier key is held down during the process of sampling, to save a click afterward. Provide an option in preferences to invert the behavior of the modifier: that is, automatically apply when the modifier is NOT held down, but not when the modifier IS held down. Allow dragging from the color well directly in order to sample and apply a color, without needing to open the popup at all.

Probably because he is not setting the normal fill/stroke color, but an additional color which is part of one of the layer FX, which that tool does not correspond to.

The panel itself technically does, though curiously when working with artistic text you need to select the text (text selection/highlight) before changing things, but sadly you can only have the standard one fill and one stroke with text - you can't add additional ones, which defeats the purpose of using the panel, and is a rather sad limitation.

Just drag a shape's entry in the Layers panel over the thumbnail of the layer you want to use it as a mask for. It remains a fully editable vector shape but is used as a mask. Alternatively, if you make a layer a child of the shape (by dragging it underneath the shape's entry in the Layers panel), it will be clipped to fit inside the shape.

In the meantime, I would suggest trying a normal Paste, then group the pasted layers and rasterize the group.

I believe that is because the OP carefully chose a set of "dummy" topics which are alphabetized in order to demonstrate the concept. That is something unlikely to occur in a real-world scenario.

The perception of color can be impacted by other colors surrounding the workpiece being evaluated. As a result, any application which deals with projects in which color accuracy plays a vital role should ideally be presented in neutral grays, to avoid influencing the perception of the colors in the document or project. A title bar takes up enough screen space to potentially influence these perceptions, so the choice to use neutral grays is correct here. If an option is provided to make the mistake of coloring it, please make sure it is just that - an option, and not the default. This color neutrality is one of the few areas where the deviation of the Affinity products from platform standards is justifiable as being correct.

I probably would have worded it "Inherited (value)" where value is the value that is currently being inherited.

The primary purpose of anchors is to serve as places for hyperlinks to jump to. From that perspective the order is irrelevant and tracking a user-defined order seems unnecessary. The problem is that Serif chose to overload these to also serve as PDF bookmarks, for which the order is more meaningful. In so doing, they should have allowed for this, but currently do not. So yes, I agree that this is an improvement which should be made, but currently the only option is to rename them if you want a different order.

Note also that there are two places to enable baseline grids: you can enable it in the View menu which is global for the entire document, or you can enable it in the Text Frame panel for individual text frames. Leaving this setting enabled for the text styles means that if you enable it for an individual text frame, it just works - if you disable it in the text styles, then even if you don't enable a global baseline grid, you would need to go back and use specific styles or manually enable the baseline grid for all of the paragraphs of text you want to align, even if you are only using the grid within individual frames. You might want to take that into account when deciding whether or not to disable this in your styles.

What Bookmarks panel? I can't find that. If you mean the Anchors panel, they are sorted alphabetically, so you can reorder them be renaming them. I was able to drag individual anchors out of a nested position; you need to drag them so that the indicator appears around the entire list, rather then between or over top of other items.

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.