lepr

Decided to concentrate on some much larger drawings this year!....(Year 8)as I never seem to finish!😀
Used New Comic Book Brush Sets combined with PB 33 (Ink Blocking) have not uploaded these! but you can use these:
Brush Sets:
Inkers: Project Brush 19 'Inker'
Patterns: Project Brush 19 'Pattern Toolkit'
01 Dream
Affinity Designer | 1000 x 500mm | 300Dpi

Tint Overlay


Grey Original

Halloween I + II Assets
 

For your particular workflow, if your document is CMYK, you need to specify K-only CMYK values (that is, C:0, M:0, Y:0) to fill your spare channel to get the spare channel to contain the values you expect. Specifying values in any other way will result in the spare channel containing values that you are not expecting.
By the way, I advise you do not use Affinity's Info panel for inspecting CMYK values in a document. Use the colour sampler in Colour panel, as you did in the first video, to discover true values.

Yes, absolutely - apologies that was in fact one of the intentions when implementing this but wasn't in the first beta build. It will be like this in the beta update next week.

The issue is caused by placing an image into a larger canvas, with fully transparent edge pixels around the placed layer.
it seems the export function starts with the actual position of the image layer at 5,52, and transforms the resample result to a fractional position.
This can be rated as bug, specifically as results from export differ from in-document resize.
This issue can be easily avoided:
add a rectangle shape in canvas size, no fill, no stroke nest the png layer as child. now the results from export and resize are identical.
i did not spot this as I missed to set resample to resample during first tests. Your video was extremely helpful to reproduce.
 

add me to the count, please

The choice of ctrl modifier there was a mistake for the macOS software. It breaks decades of UI standardisation on Mac. Mac users always expect ctrl+click to be equivalent to secondary click (typically right-click on a two button mouse). 
A better modifier for 'convert to smooth' would have been cmd. Similarly, deleting a segment of a Curve should have been cmd+click instead of ctrl+click.
In other words:
ctrl+click should display the context menu appropriate for whatever is clicked cmd+click on a node should convert it to smooth cmd+click on a segment should delete it

To emulate Preview resizing in Affinity Photo:
open an image file in Affinity Photo document convert format to RGB/32 document resize with 'Lanczos 3 (separable)' resampling document convert format back to original (for example, RGB/16 or RGB/8)  

Nice improvements.
Is there any chance that we will get absolute differences in addition to relative differences? This has long been requested with Power Duplicate.
Some easy way to make (for example) 100 concentric circles, each 20 pixels larger than the last would be a real time saver.

It would be great to add a «scale each» checkbox

Apps: All
Platforms: macOS, Windows and iPad
 
We have now added a spiral tool which is available from the shape tools flyout. This is something we have had many requests for, but also varying requests as to the type of result wanted. For that reason we have tried to make this as flexible as possible, both offering different types of spiral and variables to adjust.
When you create a spiral you will see from the context toolbar the different options available. Here are some examples of what you can create with the tool:
Spiral Type: Linear

Spiral Type: Decaying

Spiral Type: Semi-Circular
This type replicates the way many people have been creating a spiral in Affinity - effectively by joining decreasing semi circular arcs together.  With this type we also offer a counter Semi-circular option which returns the spiral back on itself:

Spiral Type: Fibonacci

Spiral Type: Plotted

 
 

Yes. It's a pain.

Hi @jubarbie,
Thanks for following up with the additional info and screenshots, when I swapped over to using a Macbook trackpad the issue immediately became more prominent with it's sensitivity fairly consistently swapping between the cursor transform modes when clicking. I've now logged this with the developers.

Yes, the slippery handles have plagued me since the beginning of v2. Has been reported before. Worked perfectly in the v1 apps, so surely cannot be too difficult to fix.

Hi,
I have this 'bug' for a long time. When I wanna skew a shape using the selection box handles the tool switches to resize tool when I click. This doesn't happen all the time.
See video below, you can see everytime I click it switches to resize tool.
I'm using the V2 beta : 2.2.1 (2075)
Enregistrement de l’écran 2023-10-23 à 14.11.26.mov

Maybe a glitch in the Matrix

To Serif Staff and @Ash
I've been meaning to write this feature request for years, and it's been partly written before by others, but now I'm doing it with passion, two dashes underneath and weariness in my soul. Because I spend too much time correcting the flaws in Affinity in my work.
There are a number of usability flaws in Affinity, and they are well-reported. I can live with some, but not with others. There are some flaws that simply must be fixed now, and not as small fixes, but in a fundamental and structured way.
I can only recommend that a future release should be dedicated to only settings, usability and workflows. That you take all these reports from customers seriously and resolve them in a serious and structured way. And give yourself the time, space and dedication to stop and rebuild some of Affinity instead of patching holes as you go.
I would just like to request two things to be fixed at this time, and at the same time I would like to ask you to have preferences expanded and structured so that your customers can avoid workarounds and endless detours to the greatest extent possible by setting good default settings in one place. Not small additions - but get it set up professionally and user-friendly.
My specific request:
In ALL my work, I want to use FX: Scale with object ON and Stroke: Scale with object. The few times the opposite is the case, I want to be able to disable it. The opposite of today. But they are not enabled by default, and in the case of stroke scaling you have to change a default for the object, which you can't do with FX. But somehow again and again I find these settings disabled. On my computers, on others... constantly.
I create lots of small and large objects with FX, and I can't believe I have to set scale with object on each one. Why on earth can't I just set defaults centrally in preferences once - and change them again if I need to use other defaults?
All the nonsense that has built up over time in Affinity deserves its own release, so you can also build architecture and methodology around the corrections, so that it is corrected logically and technologically appropriate. Preferences as of today is still pretty messy.
I am not looking for workarounds or object inheritance. Just want to enable scaling and never look back.

Probably not in a book project, but there might be real problem in an imposition job involving placing columns and rows of duplicates of a single design, and generally in printing industry 0.25 points is a meaningful accuracy at which all professional applications should aim at.
Even a small trim size error can cause visible results. The attached PDF has a standard visit card the document size of which is 89x44mm placed on a sheet that can have 10 x 10 cards impositioned. The first page has a Publisher created PDF that creates a trim size of 89,069 x 44,027 at 300 dpi document and export resolution, and the second page an InDesign created card that has trim size of 89 x 44mm (rounded from pt dimensions with accuracy of three decimals). Both cards have been exported identically. They have a 0.25pt inside aligned stroke at the edge of the canvas (not basically a practical thing, but demonstrates well enough the issue).
The positioning has been done identically: placing a single document as it is on the top left corner of the canvas and then just snap duplicating the design without extra gaps assuming that 10 cols and rows exactly fill the sheet. Which it of course does when placing the InDesign created card, but not when placing the Publisher created card with a trim page box rounding inaccuracy (which is correctly retained when placing the PDF). The error could of course be fixed easily by cropping the placed PDF before starting duplication, but it is a nuisance and should not be there. In a sloppy workflow not checking the assumed trim sizes, or in an automated workflow reading trim sizes and doing positioning accordingly it would require manual intervention, or could end up being printed.
imposition_job.pdf

A simple solution is to ctrl-click with Node Tool to delete the path segments that lie across the ends of the 'S' shapes, as shown in the video below.
 

delete segments.mp4    

Here are my two attempts at "The Whittler" illustration project from the Affinity Designer Workbook. I forgot to mention in my "Reflected Skyline" post is that every upload that contains two images from the workbooks are years apart. The V1s were done on a low-budget laptop I had since college which still works to this day! The V2s were completed on a much better system. I must admit that I could've put a bit more effort into V2, especially with the robot's neck but hopefully that'll be done if I ever decide to tackle it again
 
V1:
 
V2:

Absolutely yes.
Your screenshot shows Affinity displaying the iStock image file correctly on your machine.
I was talking about the OP's attachments (screenshot and image file) in a correctly colour managed browser and when I open the attachments in other colour managed software on my Mac. These attachments show the image being displayed wrongly in Affinity on the OP's machine for some reason.

An extremely valuable tool in Designer is Point Transform Tool. (As with all tools, look at the hint line at bottom of window for keyboard modifiers.)
The video below shows a shape being snapped to another shape, but it also works with Curve and Curves objects.
 

PTT.mp4    
 

Set red value to 0 where red value is less than r (8-bit integer):
R = stepn(R, (r - 1) / 255) * R
 

 
 
 

Thank-you! This is exactly what i was looking for.

Colour differences when resampling 8 bpc or 16 bpc image in Preview versus Affinity:
Preview uses a linear colour space for resampling to the display resolution or export resolution, whereas Affinity uses the gamma-encoded space of the image.
When Affinity is at full scale (100% zoom) and Preview is at full scale (100% on a 'standard' resolution display, or 50% on a Retina display), they are not resampling to the display resolution and they look identical.