R C-R

Right! That's why Illustrator has been such a dismal failure for Adobe. 

There is another complication, though. For some purposes (specifically printing or exporting to PDF) the order and layout on the workspace is not relevant. What is relevant for those functions is the order in the layer stack, on the Layers panel. The lowest Artboard in the stack will be page 1, the next one up will be page 2, etc.

@JhonatanS, let me clarify once again:
The Move By Whole Pixels button – which is where your red arrow points to – is designed to override the Force Pixel Alignment setting.
Please read again: 
^ This is a valid use case for Move By Whole Pixels.
But else, you want to keep this ^ option disabled.

Your screenshot shows both Force Pixel Alignment and Move By Whole Pixels enabled. As has been mentioned, the latter should be disabled to prevent the issue you see.

They seem lines but they are not.
Have a look at the attachment.
bug2.afdesign

When planning to export to pixels, everyone should learn lesson 1 first:
Always work in the Pixel Preview mode!
Repeat that after me, kids!  

There is a massive conceptual flaw in how Affinity calculates the pixel grid.
When using artboards (or pages, for that matter), each artboard claims to have its own pixel grid when you look at the ruler. 
But it doesn't.
There is something what I'm calling the "absolute pixel grid" of the whole canvas that rules it all.
The major p.i.t.a. is that in Designer, it's not even "absolutely absolut". The absolute X=0 begins where the left-hand edge of the left-most artboard is and the absolute Y=0 where the top edge of the top-most artboard is on the canvas.
Drag your top-most artboard without Force Pixel Alignment somewhere else so that it's no more top-most, and your "absolute pixel grid" may go havoc on every artboard.
It's maddening.
And don't let me even start when bleed comes to play… 

To align vector strokes of uneven values to the pixel grid without antialiasing.
E.g. a 5 px horizonal stroke will antialias if Force Pixel Alignment is on. You must position it at Y = n.5 px. Then you can activate Move By Whole Pixels so that you don't lose this fractional position.

Hi, this is a known issue with version 1 and macOS Sonoma. There is a workaround, drag the master page thumbnail onto the page thumbnail.
 

It did not for me, as I explained in my post above, & can be confirmed by experiment. For instance, consider this slice test.afdesign example. It has a single 200x200px slice1. In the Slices panel set it to 0.375x & export that slice to get this slice1@0.38.png file: 
Note that its size is 76x76 px, not 75x75 px (200*0.375).

My experience is completely different - if Help is up-to-date somewhere (corrected and added), then in the web version. The help in the application is valid on the date of preparation of the release, and it can be corrected/added only after the release of the next version, i.e. approximately once every half/quarter of a year.

More than that, to me It isn't even something that needs fixing. As you say, there is no universal place to find such things in all apps so users just has to resign themselves to the occasional need to do things like opening menus & seeing what they contain or asking in forums like this one for help when they cannot figure it out on their own.

More than that, to me It isn't even something that needs fixing. As you say, there is no universal place to find such things in all apps so users just has to resign themselves to the occasional need to do things like opening menus & seeing what they contain or asking in forums like this one for help when they cannot figure it out on their own.

More than that, to me It isn't even something that needs fixing. As you say, there is no universal place to find such things in all apps so users just has to resign themselves to the occasional need to do things like opening menus & seeing what they contain or asking in forums like this one for help when they cannot figure it out on their own.

But not necessarily the OS. I am still on Catalina. I would not be confused by the words "Settings (or Preferences)". 
 
Try using more software. You will find it all over the place. Serif PagePlus used to have it under Tools/Options. As did CorelDraw, OpenOffice. Canvas was File/Preferences. LibreOffice on a Mac/Catalina, has LibreOffice/Preferences. But it also has Tools/Customise, where things like keyboard shortcuts are configured.  
I think of all the things to complain about, the single idiosyncrasy of where to find Preferences/Options/Settings is very low on my list of things which need "fixing". 

It's likely a security check, probably to prevent SQL code injection.
Type your text. Screenshot it. Post the screenshot as an attachment to your post.

Yes, Apple changed it, this happened last year with the arrival of macOS Ventura.
The change was made by Apple so that this area of macOS was more in line with Apple’s iOS devices.
The position of Settings in the Menubar is still the same as it was for Preferences in older systems; under the apps Name in the Menubar.

This would be a nice feature. But, as it stands now, there is no "info" panel for a layer in which you can designate its printing vs non-printing status. What you can do, however, is to use "Layer States" to set a global on/off switch for layers you want to turn off prior to printing or exporting a PDF, etc.
The easiest way to do this is probably to create a "Smart State" using (for instance) a color label. For instance, on a document-wide basis, mark the first non-printing layer as Red. (Right click on the layer, and choose the Red swatch at the bottom of the drop-down menu.) Open the States panel and create a new Smart State. When asked for a name, call the smart state "Turn OFF Red layers" or something similar. In the panel, check the top filter "Layer tag is…" and click in the Red circle.
Now, you have a way to designate that layer, and any subsequent layers you create, as non-printing by turning the Layer State to "Hide" or "Show". Before printing or exporting, simply turn the Layer State to "Hide" - turn it back to "Show" when you're done.

An alternative method using Spiral Tool and not requiring Point Transform Tool:

heptagram.mp4    

The amount of noise heavily impacts the size of the png (maybe also other file formats, i don't know. I usually use png).
The resolution isn't always the biggest factor of the file size. A 10000x10000 picture of just one color is only a little over 310kb when exported as PNG. Add 5% of monogramatic gausian noise and it's almost 67MB. Non monogramatic makes it 127MB. All same resolution. just different pixels in it.

Hi @Karl Toon,
Would really need to see a copy of the file you are exporting in order to see whats going on.
As you've not mentioned which Affinity app you are using, can you upload either the afpub, afdesign or afphoto file for your project to our Dropbox here and we can look into why it's being flattened on export.

There are many kinds of ordinary layers. As yours is behaving in a way you don't expect, we need to see more information in order to help you. Otherwise we just have to start guessing about what you might have, and what you're seeing.
 

I think you are right about that. This new in V2 option seems to confuse quite a few users. More about it can be found for example in this Move Tool help topic.

@diederiks, are you running any third party 'helper' apps that might have an effect on what you can select or how the mouse pointer works?
If for testing purposes you create a new user account & log into that, does the problem still occur?