Michail

What you can do is copy the contents of the selection in a reduced form. To do this, press Ctrl+Shift+C (instead of Ctrl+C), or use the corresponding command in the Edit menu. Then paste the content back from the clipboard (Ctrl+V). This way, the image layer is preserved if necessary.

The pasted content is an image layer with special properties. Rasterise the layer in question after pasting to convert it into a pixel layer.

If I use the PNG images seen in your post, it seems to work fine here. For the PDF export, I used the default settings. Are you sure that the QR PNGs are to blame? Can you provide the afdesign document? Maybe there are other critical elements in your layout.

Can you provide a little video so we can see what you are doing?

It is not enough to insert a gradient overlay. You must then also create a gradient in the image . The same applies to the brush overlay. Here you use the "Overlay Paint Tool" .

Welcome here to the forums There are reports that V2 files can no longer be opened if they are on a network drive. However, I know of no reports that this is also the case with V1 files.

1.) Levels: 2.) Colour Balance: Result:

I am aware that you can customise the tools. However, it is surprising that the double-click only works for the individual tools. It's not a big deal and I just wanted to mention it. It's an inconsistency between the programmes. I've also been wondering since the beginning that only in Affinity Publisher are the two thematically related tools next to each other. As I said, I just wanted to mention it

With a double-click on the zoom tool, the 100% view was previously obtained, and with a double-click on the view tool, the fitting view. Both no longer work in Affinity Designer 2. In Photo and Publisher it works as expected. Furthermore, both tools are now in the same tool flyout, which may be intentional. The developers may have worked in this area. Therefore there might be a connection to the following thread:

Can you describe a little more precisely what you are doing (step sequence, PDF settings, etc.)? If you are placing files and not screenshots, please provide us with one of the original files.

I can confirm the behaviour here. However, this happens to me in Affinity Designer as well as in Affinity Publisher.

Pardon, I did not read carefully. I assumed that there was already an installation on C:\

You can move MSIX programmes to D:\ after installation (Windows settings > Apps).

... of course not! But it shows the intentions. But it could also be a bug that has not yet been fixed on the Mac (unlike Windows).

Here is an excerpt from the (Windows) help: Develop Persona gives you access to the following: Output options that will retain your original raw image as a non-destructive raw layer, with the raw file either embedded (copied into your document) or linked (left in its original file location). Develop Assistant to control behaviour on loading the RAW image: choice of RAW engine for RAW processing enable/disable automatic lens correction (SerifLabs RAW engine only) enable/disable automatic noise reduction enable/disable automatic tonal adjustment (curves) enable/disable automatic exposure adjustment Tonal adjustments using the Basic and Tones panels. Sharpening and Noise adjustments using the Details panel. Lens correction adjustments using the Lens panel. Overlays for applying adjustments to specific brushed image regions. Crop Tool for cropping your image. Blemish Removal Tool for correcting image imperfections. Focus panel. Scope panel. Snapshots panel for comparing different image processing settings. At any point while working with an image or any selected pixel layer, you can switch to Develop Persona to make use of its unique features.

The video was apparently produced on a Mac. It would be interesting to know if this is also the case for the other assistant settings. If not, it would be inconsistent again, and therefore not correct.

I know …

If you see no benefit in it, I fully understand, although I cannot understand your reasons for doing so. Other users - like me - would very much appreciate such functionality. I gave a few reasons in my post above: By the way: the term non-destructive in this context refers to the fact that you can get back into the Develop Persona at any time without losing your settings. Anyone who shoots in RAW format and uses RAW converters should know the difference between the raw data and JPEG or TIFF.

This is indeed the case with the tone value curve. But this was inconsistent within the wizard in V1. I think that manipulations with preview should be in the panels. I remember a discussion about lens correction. It was initially only in the wizard. But people didn't understand that there was no preview. Later, Serif added an option in the lens panel. That's how it would have to be done here. The wizard takes care of files that are opened and the panels take care of editing - with preview.

Thank you @Pšenda. I must have missed that - or forgotten it again. It looks like there is a connection with externally stored files. In this respect, it would be interesting to know whether @CWR's Publisher2 file was stored on an external storage medium.

Is it known what is causing the error?

Thank you! I can confirm the process - but have no explanation for it. Perhaps it will be of use to the developers if you make the protocol available to them. You can find it (in Windows) under %userprofile%\.affinity\Publisher\2.0\ --> Log.txt

Welcome here to the forums Can you provide us with the Publisher2 file?

@albo49: Welcome here to the forums The development assistant is not an editing tool for opened images. In the development assistant you define how a RAW image is to be opened.

But there weren't all these mini objects flying around before the second attempt. Were there?