ericosmosNEW

That's fine - I just wanted to give you a bit more information on what I found whilst trying to reproduce the issue.

Of course it is an important issue to solve and it is with development to be fixed!  

This is logged with our developers, so I'll be sure to 'bump' this report with your post now

@Wosven ah, perfect. Exactly what I was looking for. thank you.
@Komatös yes, just with some more space between column edges and text. Wosven's suggestion worked perfectly

Actually the issue isn't in the preset but with any version from PDF v1.5 and above and occurs if "Embed profile" is activated. If unticked then also a non-X PDF will export with overprinting and with this certain black swatch as overprinting black. As compensation / replacement you can activate "Convert ..." to avoid unexpected results if the viewing or printing app uses a different profile.

 

Actually this isn’t as much as problem as it first appears, here is the workaround:-
1. Create your shape or import the image that you want to duplicate the pattern from, for ease of use here I just use a shape from the shapes studio but any image or shape layer will do.
2. From layers studio select New Pattern Layer, just accept the default parameters as they are unimportant. EDIT: Actually it is, if it is a very detailed pattern pick a larger size eg 500x500.
3. Move the pattern layer selection box over the area you want to create the pattern from, use the resize handles and snapping if needed as you desire.
4. Move the pattern layer below the shape or image layer
5. As James Ritson does in his demo video, use Merge Down and Bob’s your Uncle, pattern created !

IMG_0760.MP4

Yes! Exactly what I was looking for. Thank you 🙏

Yes, but it doesn‘t help much when you want to paint within the selected area without the distracting marching 🐜 

Pretty easy on my iPad…. Note rectangle CMYK set to 50% black to 0. Use colour picker and note settings have now changed the initial settings and reintroduced black.
IMG_7444.MP4

I don’t think it is a .afphoto file problem because it is happening in every file.
So, if you fill a space with a grey that you have created with the cmyk sliders only from cm & y (So, black is 0), your color picker will identify that color with the exact same values and not suddenly add black (k-values) while reducing the cmy values? Could you demonstrate that to me in a video?
To me it looks like Affinity isn’t honoring the cmyk numbers and deliberately changing the cmyk mix for whatever reason.

It worked! Thank you again 🙏

Thank you. I know how it works, but the file I want to import is greyed out 🤷‍♂️

sorry, I seem to have missed that I was on an iPad thread and gave an answer from the desktop version - agree this seems to be missing on the iPad

Back to the main-topic:
What do you think serif will get fixed first?
The magical mysteries of hardware-acceleration (Windows) or the rocket-science like riddle of locking layers (to protect them against any change) ?

Hahaha!
I am not against trial and failure, but simple things are better left simple.
Like shift-click. Shift works as angular guide/lock all over the place.

It reminds me of the old tale about NASA who proudly showed the Russian cosmonauts their new zero-G-writing-fountain-pen that they had used serious manpower and dough to develop. The Russians calmly pulled up a pencil: "We use this".

Suggestions like these are the perfect example why some stuff in AP is just plain broken. That has got nothing to do with Adobe indoctrination (I don't care either way, I never used Photoshop). A bad workflow is just that, a bad workflow. Drawing straight angled lines on a pixel grid should be a matter of a few clicks and easy as pie. Period. If you need to first create a vector object, then rasterize it, something's already gone horribly wrong – let alone if you have to switch to an entirely different app and back again.
There may be tools in AP that work better than Photoshop's, or that just work differently. I applaud that. I have no preconception on how things should work, other than that they should work and that tools need to enable me to do my work efficiently. If that requires learning or re-learning, fine. But the pixel and brush tools are not examples of that. As far as line drawing is concerned, more than half a decade after AP was first released, they're simply still not working right, to the point of being useless for some types of work, as is well-documented in this thread.

Hi, is this issue still being considered?
I find it dangerous that a locked layer can still be modified. And as shown by all the forum posts over the years, it goes against the principle of least surprise. A lock in almost any other software implies that the layer is read-only, with a partial lock requiring further and explicit steps. Despite the argument that layers can only be selected intentionally, it is easy to select the wrong layer by accident. It has happened before to me, it will happen to others.
I'm loving the Affinity software suite and have recommended it to others. However, having such grief knowing that it could have otherwise be avoided and reading that it is "by design" makes me wonder which other surprising decisions might be lurking around. Please, no bad surprises.

@MEB
You invited me to add my voice to this posting and explain my request for a "full lock" for layers:

In Designer and Publisher we work with objects, parts, components, whatever you want to call them, which we place and arrange on a "sheet".
Usually thoses Elements (each of them is a layer) do not cover the whole "canvas"/sheet... but just a part of it.

Because of that I do understand, that you see a certain "risk" of selecting an object (= layer) by mistake during "canvas-interaction".
(Although I think in complex projects with many groups and layers, it may be easier to find and select
the desired layer/group in the Layer panel than trying to click the right object on the canvas..esp. if they overlap)

BUT:
Photo-Editing is not (or just very very little) object-based work.
In Photo-Editing we ususally work with layers which cover the whole canvas = very little to no risk of selecting a layer by mistake.
In Fact: in most situations you have to use the Layer Panel to select a layer since its covered by other layers and therefore can not be selected directly by canvas-interaction.


But even without this explanation, I think a complete, full layer-protection against any manipulation is a useful and missing feature - Please add it to all Affinity Apps.
It does not hurt - but may help.

And more:
 

As many users' requests show, this is not a suitable/sufficient design. This design assumes that the project has only a few layers, so the user can watch them. However, if the project has thousands of layers in many nested groups, it is difficult to see their content and their unwanted selection/changes. Then it is preferable (and so expected and assumed by the user) that locking the layer ensures that its content is protected, and that the user no longer has to worry about it.
The solution could be so simple - if the user selects a locked layer in the Layers panel, a dialog/query "Do you want to continue editing the locked layer? Yes/No" is displayed. Alternatively, this behavior (query and confirmation before editing a locked layer) could be enabled in Options. I would turn it on immediately :-)

Stumbling over not really locked "locked" layers a couple of times, I sign in here. I would prefer a more detailed locking (like in Photoshop) as mentioned above, too!
This is not meant as rant, but I question why some features are implemented only half way. I find it obvious that a layer lock should completely protect a layer from unintentional access. There should be at least one additional function to do this. Like I said, not meant as a harsh criticism, just wondering.

Definitely need a better lock!!!

A lock should be a lock, a real lock...

Has hiding the selection line been asked about before? I used this a lot in PS and it was very helpful when tweaking/aligning the image portion to see behind the marching ants. Also, even though I'm impressed with the image adjustment tools, some buttons for moving a single pixel at a time would be useful as well.
Thanks
 

Yup, saving channels makes sense if I want to reuse them. But I am doing lots of quick, ephemeral selections and I can't judge the result as long as marching ants visually interfere, especially with complex selections. I hope we'll just get the "hide selection" button eventually.