lepr

Ensure the Move Tool is active and the Picture Frame is selected, then Lock Children should be the rightmost control in the context toolbar. If you see a double chevron at the right hand end end of the context toolbar, click it to reveal controls that overflow the width of the bar.

If you disable "Edit All Layers" at bottom left of Layers panel and select a member of the Group, then pressing cmd+A (ctrl+A on Windows) will select all members of the Group. Edit: and welcome to the forums

Using Ellipse objects, same as the OP: Copying from beta 2.6.0 and pasting in retail 2.4.2, the grouping is maintained for me (Intel iMac). I do not have 2.5.x, so cannot say what would happen there for me. Pasting in retail 1.10.8, the objects become ungrouped.

I think the tool is reasonably reckoning that you must want a visible stroke if you deliberately enable ‘use line style’, therefore it sets a default stroke of 1 pt black instead of using the 0 pt no colour.

The right hand end of the context toolbar of Pen Tool has toggles for 'use line style' and 'use fill'. If you see a pair of chevrons at the end of the bar then there are more controls which become available by clicking on the chevrons.

It is a bug since way back in v1, and there is a workaround. The bug is that transparency in an object's FX Gradient Overlay incorrectly affects transparency of the object, instead of just the overlay, if the object is clip-nested in some other object. An Artboard is a clipping object, therefore its content is subject to the bug. Fortunately, there is a workaround which tricks a correct rendering without requiring a change to the structure of the document: add an invisible opaque FX Colour Overlay to the object that has transparency in its FX Gradient Overlay. An invisible opaque FX Colour Overlay can be achieved by black with blending mode Add, or white with blending mode Multiply.

There seems to be a misunderstanding about the problem. Auto-select options do not help. There is a regression in 2.6.0: https://forum.affinity.serif.com/index.php?/search/&tags=AF-5999

Sorry, I missed the bit where you said it works on your Mac.

The technique you tried in your video works correctly on my Mac. You shouldn't need to use the more complicated method shown by Bruce.

Yes, I get the impression James Ritson got the job.

Yes, clearly, and that is why I said it's possible that Serif is not an attractive employer.

It's been like that since v1, and I suspect it will be classed as "by design". A workaround is to enclose the aliased object in a Group then rasterise the Group.

The solution would be the developers restoring the previous behaviour. Hopefully the bug will be acknowledged by a member of staff today.

There was a recruitment ad several months ago. It’s possible that Serif (Canva Nottingham might be more appropriate now) is not an attractive employer.

Certainly not universally true. Rasterisation of vector objects can be avoided in the cases of FX Outer Shadow and FX Outer Glow.

I see the same unfortunate change.

A Constraints Group really is a vector Rectangle with no stroke and no fill (although it can be given a stroke and/or fill after being created). A particular problem with the implementation is that it can crop off part of the stroke of a child object and then workarounds have to be contrived.

I would describe the rasterisation of your Group as a bug. There is a workaround: instead of the FX being on a Group which contains various objects, put the FX on an invisible Rectangle which contains these objects. (My "invisible Rectangle" is a vector Rectangle with no fill and no stroke.) Try to export to PDF edited.afdesign Try to export to PDF edited.pdf

Exactly the same for me. 2.4.2 is needed for good stroke expansion.

The new behaviour is in the last beta too. I didn't have FPA enabled when testing for it before, so it didn't affect me. Normally I opt+drag an object or use Duplicate command to duplicate an object, anyway, and so there was little chance of seeing the new behaviour until reading about it. For a pasted non-rotated/skewed object with stroke, it seems to be the top left corner of the bounding box that would contain the expanded stroke that gets aligned with the pixel grid.

I hadn’t seen that thread, but I’ll test the various scenarios described there when back at the Mac.

I’m not relying on my eye. I have 6 decimal places for pixel measurements and there is zero movement of the pasted object in beta 2.6.0 on my Mac. Edit: now I realise that the movement does happen when Force Pixel Alignment is enabled.

Not at all. I've slightly re-worded my comment because it was ambiguous. The bug is not in the last beta of 2.6.0. It is new in the retail release of 2.6.0.

Wow! I am not seeing that bug in the last beta of 2.6. A familiar story in Affinityland. Ah, I did not have Force Pixel Alignment enabled. Now I see the new behaviour is in beta 2.6.0 (3134).

Yes, the workaround only works correctly when the scene behind the group is opaque across the entire canvas.