Zero1

Thanks, obviously my search term was not good enough

Yes, i am using Aphoto, the first one was indeed from V1 but as @lepr pointed out, it is because of the blue blend range why it is turning black when you turn off the HSL.

Thank you!! Missed that one.. It would be nice if Affinity would show the colored curves in the blend ranges (similar to a curves adjustment) so that you can directly see that there is a difference.

I have attached a document where it looks like the groups are an exact copy (at least i cannot find or missed the difference). Group1 is from an old document which i copied over... Group 2 is one i created from scratch... Any one an idea what is happening? Group-acting-differently.afphoto

I think title is self explanatory. I searched forums if this was already known but couldn't find anything. In the attached image you see that when the HSL is being clipped by a rectangle, the blend range is not applied.

@Lisbon I believe the transparent areas are treated as black (value 0), which then makes sense why everything is divided by 2 (with alpha 0.5)

When a procedural texture is applied to a curve object (eg. a rectangle) and the alpha value is changed (eg. 0.5), i would expect it would only affect the curve object's alpha, however the alpha is also applied to the layers below. When i lower the alpha of the rectangle with a curves adjustment, it only affects the rectangle as expected. See the screenshot, where on the left, the alpha of a red rectangle is halved with a curves adjustment. The blue background is not affected. However doing the same with the procedural texture (live) filter on the right, the alpha of the blue background is also affected. Initially I thought this only happened with the Alpha, but the bug also exists with RG or B. Then i rasterized the rectangle and applied the procedural texture again and it still happens. So it looks like the procedural texture (live) filter propagates down for the transparent areas even though it has applied as clipping layer. I would expect, because it is a clipped child it would only affect the parent (like the curves adjustment). I assume this is a bug unless i am missing something here? PS. Using the latest v2.04 (mac)

How can you do a Pixel Art resize only to a layer?

That is why this post is in macOS Beta forum

You are completely right! Which brings us to the original question A checkbox is being hidden without reason... which is bad

Haha, that is true, but still think it is detectable whether the merge is going to apply to the "parent" image or a child pixel... (at the end it applies to something and is processed if applicable, so it can be detected too...). Maybe hiding the button would case confusion (why not shown etc), but rasterizing the image layer would make sense.

Thank you... missed that But in order to do that, i think Serif has to be very clear what is fixed/updated and not add a text like: - Assorted other fixes

That would be perfect also

Thank you for clearing that out.. that was also my expectation (destructively applied(, however as i am mostly working with image layers, nothing was happening. Pixel layer was the magic word here I would suggest that when the filter is a child of an image layer, to hide this button or have the image layer rasterize to pixel (with a warning from assistant), which would make more sense. Secondly it is kind of strange behaviour when the (blur) filter in on top of image layer and a pixel layer is below it. The image layer gets blurred when merge is pressed, it skips the image layer and merges with the pixel layer below. It makes sense but i don't think that is expected behavior.

Let's agree to disagree on the matter of whether it gives a better overview or not (less/more room). On the matter of the V1 Layer remark, the width of the panels can be controlled, so the full text can be made visible if needed and indeed i do add them now in the title when i change the title (which i was not doing when using v1) Again it is not something critical, i just wanted to point out that when show object types is turned off, it becomes very difficult to notice the difference between pixel and image layer (without hovering). All the other layers have their own icons and are easier to spot.

Thanks for pointing that out carl123 and i was aware of it, but as you can understand it is not very practical to hover over each layer you have to find out what it was, don't you think? Secondly it does not help to give a quick overview what is what, in 1 look.

When Show object Type is turned off in the layers panel, it should show the object type after the layer name (as in V1). Now it is all or nothing and when the show object type is turned off, there is no way to see the difference between a pixel and an image layer (which can be quite frustrating, as depending on pixel or image, things work differently...) Showing the object type after layer is also useful when filters eg are applied and titles were changed. It now shows a different icon for each filter applied (right v2) but in V1 (left) it was much easier to see what filter was applied. Even if you would know all the icons by heart, on a big screen you really need to focus to differentiate the icons, where as text, it's super clear. I do like the icons (looks much better then v1) but i think the filter name should be printed after layer title (when Show object type is turned off)

When using the Live Gaussian Blur, the preserve alpha checkbox is available when it is added. After closing and opening it again, the preserve Alpha checbox disappears? (Same happens with box blur and probably with other blurs too) Also interesting enough, after pressing the merge button, the filter is blocked for editing (the edit dialog does not come up) until you select another layer and switch back, then the edit dialog comes up again? BTW any idea what the merge button does??

I believe this issue also exists in the production version and is not solved in this Beta. When you are recording a macro and select a layer above you get the message what to select eg. However after pressing Select, it asks again? And things gets confusing.. Especially when working with child layers etc.

Actually as GarryP mentioned, the global source is exactly what you are looking for. You can open up a document and use the clone brush and select the source and then press add global source. In the other document you can now use the global dropdown. You can add multiple global sources and with the sources panel you can select the source which should apply when using the global dropdown. Check out (around 7.40 the global source is explained)...

Searching in Library (Macros), kills the application. Tried multiple times and sometimes it works but then mostly the second search kills the app.

Searching in Library (Macros), kills the application. Tried multiple times and sometimes it works but then mostly the second search kills the app.

I think this has been requested earlier (for v1), but it would be great time saver if you would be able to assign keyboard shortcuts to a macro in your library. Or maybe ability to create a shortcut to the search in the library and then apply the macro with the return key (if only 1 macro is left from the search)

I was just going to say the same You can temporarily hide the layer to select the source area from the layer below.

Thank you for sharing!