R C-R

Again, the HSL tool isn't really designed for Grey tones.
Have you checked the Helpfile page for the Selective Colour Tool?
There are also tutorials which cover every adjustment in Affinity, such as:
 

If it opens in Publisher, can't you just do a File > Edit in Designer at that point, rather than copy and pasting?

From personal experience. If the hidden files are shown, I can inadvertently do a hell of a lot of hard-core serious damage to my computer's ability to work. I would turn it back to having the hidden files hidden.

Combinations (collections) of specific colors can be copyrighted, though.

Because, as far as I know, only makes sense when the Palette Colours are associated with their respective physical buckets of paint.
Those physical buckets of paint which you can more or less easily order and use in your printer.

Except for the 25% discount on the V2 Universal license if you previously registered a V1 purchase of any of the Affinity apps.

upgrade from v1 vs buying the programs for the first time.

They have aggressive licensing to either buy the universal license for 120 or 160 respectively or buy AD for mac and windows for 140. DXO is not like that; the nik collection works for windows and mac.

As annoying & unhelpful as it is, since V2 supports quite a few new features that V1 cannot, it isn't possible to add a fully functional option to save a file created or edited in V2 to save it in the V1 format.
What this means is to collaborate with V1 users you have to do all the work in V1; otherwise the V1 users won't be able to understand how certain tasks were accomplished, much less be able to open the files.
 While understandably that is quite inconvenient & annoying, it is certainly doable because the V1 & V2 apps both can be installed & used side by side.

See AF-359.

I have seen that mentioned before in the forum but what I meant by typo (since corrected) was he wrote V2 when he meant V1.
That said, since the V2 apps can share across all 3 apps via linking some resources like brushes, assets, & so on, in practice V2 can require substantially less disk space, not for the app itself but for those shared items.

I have seen that mentioned before in the forum but what I meant by typo (since corrected) was he wrote V2 when he meant V1.
That said, since the V2 apps can share across all 3 apps via linking some resources like brushes, assets, & so on, in practice V2 can require substantially less disk space, not for the app itself but for those shared items.

The main criteria for the parent layer (to allow a clipped child layer becoming visible) is actually:
the curve must enclose an area. Open curves are kind of automatically closed by a straight line from end to start node. The actual colors for fill and stroke do not matter (except coloring that parent layer - no impact to visibility of child layers) The stroke is always added in the specified order. So it is correct that a stroke in the wrong order may cover the clipped child layers with its color. If you use a semi-transparent color, child layers will shine trough partially. it can become more complicated by using Layer FX or appearance panel / multiple fills and stroke, or by using vector brushes in Designer, or by using arrow heads as decoration.
The „dual personalities“ of curves wrt their fill (enclosed area) and stroke (additional coloring along the curved edge) are a fundamental principle, but the rules are sometimes unintuitive and leading to unexpected results. 

I know you said it is working properly now but the apps should not be continuously trying to access Affinity's servers, so if there was any indication that was happening, it might be a good idea to try to figure out why they were.

A different application from a different company has different tools which will work differently.
I explained how Publisher works to change the colour of selected text.

Personally, at this point I would not like to see Serif spending much time & resources trying to implement anything like Blender's scalable interface when so many other things need attention.
But for the life of me I cannot see why they could without too much time & effort just boost the contrast throughout the UI, which would go a long way in making it much easier to use.

I think you are right about that.To check, the OP can set the decimal places to 4 or more in Settings > User Interface & the Transform panel should show if everything is pixel aligned or not.

FWIW, when I open the A2-leer.afpub file in any Affinity V1 or V2 app, it has 13 document pages & 1 Master page. As @Return mentioned, one way to see that in AD or AP is to refer to the navigator at the bottom of the window to the right left of the status bar.

I will wager this is a Pixel alignment issue. Check the x, y alignment and width and height of the picture using the Transform panel. If you are cropping the image at stage in the editing process this may result in fractional pixel values for the x, y and or width height. That in turn will result in the white line you are seeing.

That won't work because as soon as I choose that preset, the app crashes.

Thanks for that! Before I read your post I ended up deleting the whole export_config.dat file, but I'm sure your clever workaround would have worked.

I think you mean CMD-Shift-5, right?

I think the cornertool is meant here and as @thomaso said,this is only in designer.
But if you have the 3 programs installed it is also to be found in the designer persona in publisher.
 

My favourite example still hasn't been fixed. Alter a preset and if you have the light interface then there is no indication that you can overwrite or make a new preset.


This is just unacceptable.
 

Hi @R C-R,
I looked at the export dat file and made an other solution 😋
The way to remove the preset that is causing a crash is simple!
1. make in the slices panel a simple setup with png 1x and jpg 1x save it under the same name "test" (overwrite yes).
2. now open the preset again select the whole panel and remove the preset you just made.