KarlLegion

Hi KarlLegion,
This is a known issue that is currently logged with our developers to be fixed in a future update. I apologise for any inconvenience this might cause you in the meantime.
Thanks
C

Not yet. But I generally avoid working with pixels on artboards. @walt.farrell👍 had a good point about that that he mentioned earlier.
Speaking directly, layers of pixels in the artboard - this combination usually causes problems.
But I'm sure that if there is a way for that "pixel selection invert" problem you are pointing to, someone on the forum will find it.
And it will happen sooner rather than later, because there are several guys on the forum who do a great job in finding creative solutions to various problems, and here it is worth noting that these problems do not always mean that we are dealing with a bug.
That's all, a good day to you sir, @KarlLegion

@KarlLegion,
There are two workarounds to avoid the problem you're describing:
Turn of the "Lock children" option for the Artboard before resizing it.
This will allow the pixel layer to be resized with the artboard.
To avoid stretching the pixel layer either in horizontal or vertical resize the artboard by holding SHIFT to preserve the aspect ratio.
Before resizng the artboard, extrude out the pixel layer from the artboard in the Layers panel.
Next resize the artboard and at end place the pixel layer back as a child of artboard layer.
Using the second method you don't need to worry about ruin the pixel layers aspect ratio and stretching.
Personally, I find the second method more convenient and that's what I usually use because I simply don't have to use the Shift key when I resize the artboard.
 That's all, wish a good day sir.🙂

I think that's the first you've mentioned CMYK, which adds other considerations as the Blend Modes are defined based on additive RGB processing, not subtractive CMYK processing, and may behave differently than you would expect when used in CMYK. I don;'t think that's the reason for what you're asking about here, just something to be aware of.
E.g., 
 

It is actually clipped by the artboard, and this is core functionality that child layers get clipped to the parent layer.
No bug.

My best suggestion is don't mix Pixel layers and multiple Artboards, especially if you need to make pixel selections. They really don't seem to be designed to work together.

You're trying to move the pixels outside the Pixel layer, which was originally clipped by its parent Artboard and created with a size limited to the size of that Artboard. When you enlarged the Artboard you did not enlarge the Pixel layer, and the pixels you're moving become invisible when you move them outside their layer. 
I can't say for sure whether it should work that way as far as visibility of the moved pixels goes, but it's one legitimate way to handle pixels that are moved outside their layer, I think. 
It's similar to painting outside the canvas when you have a canvas rather than an Artboard. Anything outside the canvas is invisible, unless you enlarge the canvas by Unclipping it. 

Thanks both @KarlLegion & @walt.farrell
I've logged this with the developers.

Before this topic gets all dusty and forgotten, I'm attaching a screen recording (I restarted 4 times; I don't know why it crashed so quickly on these attempts; it usually takes longer).
There is no crash report, at least I didn't find one.
The only trace leads to .NET via Eventviewer, which @Lee D has already mentioned.
I hope that it helps to uncover the problem.
20240412 crash colour picker.mp4

That's interesting, and certainly seems to be a bug, Karl.
I played a bit with it and did the following:
Created a Rectangle, then applied a Contour using the Contour Tool. Created a second Rectangle. Used the Style Picker on the Rectangle from 1, and applied it to this rectangle. The History shows two entries for step 2: Add Rectangle, and Apply Object Style, as expected. Undoing (Ctrl+Z, or in the History panel) back to Add Rectangle leaves the Contour as you mentioned. I then created a Triangle, and applied the Contour via the Style Picker. This time, the History shows only 1 entry for Add Triangle Rectangle. It doesn't show the Apply Object Style at all, and Undo simply deletes the Triangle. So this seems to be a related but different situation than occurred in step 2. Here's a sample file from 2.4.2 on my Windows system:
 
contour-undo.afdesign

It's relevant. The situation is similar to this past post:
For the reason why the background all went black, it involves a bug which they didn't fix since v1 which tints the whole semi-transparent area with the outline colour. Someone reported it but I can't find the post, sorry.

But it is. I copied the layer to APhoto, selected the Alpha channel and fill it with white. Copied back to Designer and it works as expected.

I agree with @philipt18 on the benefits but the site needs a professionals area, in general. Typesetting (but a bright broader?... print design maybe?) could be one sub in such an area.
May I also point out to staff it would not only better show to you how your users actually solve their daily problems, make proper use of the suite, but show painpoints and room for improvement in a more straightforward way. Right now we can only assume how others actually work. Anyway, it woukd show to everyday visitors the software and its real world usecase beyond just the occassional tutorial.
Also, it allow users to interact more one on one without being lost in technical support jargon and exchange critical insights. Right now that energy is wasted because it often gets hidden in offtopic dialogue. The prominence of which just shows the community is being underutilized.

Hi,
When I use colour picker in the colour wheel, Affinity (Photo + Designer; Publisher seems not to be affected) crashes almost every time.
Is this a known problem? Are there any settings that need to be made?
I guess it's not a PC Problem, it meets the requirements. I'm using Windows 11.
Thank you for your help.
 

I'd love to move away from Adobe Photoshop and use Affinity Photo for all my painting, but I just need one feature to make the switch, Affinity needs to let users Clip a layer to a group. I've made a video showing off the feature, examples of using it, and why it's a must have, please check out the video and consider supporting this feature!
 
- Neil

Just wanted to post a quick update on this. Our developers have confirmed that it's a bug and will be fixed in an upcoming update.
Thanks for letting us know.

I've now replicated this on Windows and logged this with the developers.

Hi Karl, I just tried this using Publisher 2.3.0 on an M1 Pro with Sonoma and I can't duplicate it. I was able to right-click and ignore spelling mistakes or select a suggested replacement.
Could you please attach a crash report as it may be helpful for Serif.
 

Publisher, V2:
Hi, can you please change this: in any area where there are values (for instance, Paragraph window, Character window), when I scroll over it with the mouse, it changes values on whatever I touched before. For instance, I decided to change, let's say, left ident value on some paragraph. Then, if I scroll down to see, let's say, Drop caps, left ident value will change as I scroll. This is so annoying! This was the case with V1, too. This is a big problem, because sometimes I do not notice that the value has changed by itself and it damages some smaller area of the 300 pages long book, without me knowing it.
Maybe there is already solution to avoid this, but I am unable to figure it out.
Thank you

Another simple way, I hope someone could develops an addon or a plugin that helps embed stable diffusion into Affinity UI, like some devs did for Krita, Photoshop, Gimp

As herhey mentioned there's a ton of open source projects which can do people and object recognition to a high standard of quality.

I think AI is very useful for selections (subjects, sky, objects, etc)

Tools like sharpening etc is something we could want easily to be included in future Affinity updates. I do a lotto old photo restoration and while these tools can have variable quality they can do a lot to making some photos usable or retired in a way manually is impossible so I am all for it. It's the AI creating the whole photo or illustration I think is the wrong use for the technology. 

Do you seriously think it is reasonable that a simple task as exporting an image for the web coming from a 1080x1080 pixels template requires a seasoned designer with 30 years of experience in computer graphics to check the documentation in order to understand how it is supposed to works?
I can see it's a design decision and that the output is consistent with that decision. I'm saying it's awful user experience as it collides with the meaning of "pixel". Resolution doesn't belong to a raster workflow with pixels as units. The current design fails to address that.
Vectors have to be rasterized to be exported as bitmaps, I know, but when users pick a template set to pixels or create an image with pixels as units for screen delivery, they expect pixels.
I'm going to leave this thread alone and stop repeating myself, but please Serif, revisit this design and consider some options that don't mess with pixels and resolution when screen units are used. I'm sure there are ways to do it without breaking the valid use cases (i.e.: export for physical media).

At any rate, it's a conceptual mistake to change the pixel size because of the resolution on a image targetted for screens. Want to tag the image with the resolution for applications that use physical sizes? Fine. But if I want to create a 1080*1080 PIXELS image, I want 1080 pixels, resolution aside.