Paul Mc

@carl123 Bingo!. That screen was switched off though. It is strange that it works that way. Thank you. I feel a bit stupid now for not checking.

I can create a QR barcode using the QR code tool in Affinity Designer however it is stuck on the default value (the Affinity web address). Clicking on the Data button does not reveal the dialog box that I have previously seen so I'm unable to change the value. Further testing shows this works as expected in Affinity Photo and I'm able to create and copy that across to my Designer document. One strange thing that might not be related is that when I click on the Data button I see a small crosshair appear at the top left of the document canvas. Version 2.5.3 on Windows 10.

Are there any plans to provide access to the error correction level value when creating QR codes? I've been asked a couple of times by clients wanting to drop their logo or a symbol in the centre but the current error correction level makes the barcode unreliable/unreadable.

There are a few weird curve nodes in your outlines that I suspect are causing the artefacts. e.g. for the large white "spike" on the 'S' of Sheriff - if you zoom into the curve near the base you will see this: Deleting the square (Sharp) node changes the curve very slightly but also removes the artefact. It might be worth zooming into the other locations to see if there are any unusual node positions and or types that are not perceptible at normal viewing scale. Update: Checking the other artefacts that I spotted show that they all have two sharp nodes very close together where the issues are visible after export. (Also note that the problem is due to the curves being flattened - the same effect as Expand Stroke in the Layer menu). In all the cases I saw, removing one of the nodes fixed the issue. Of course, this may alter the curve a little but my eyes could tell the difference in most cases.

These types of QR codes rely on a high error correction level. This then allows you to effectively "destroy" or obliterate part of the barcode and it will still scan because there is redundant data elsewhere in the barcode that allows the whole data value to be reconstructed. The error correction section here has more info https://en.wikipedia.org/wiki/QR_code As far as I can see there is nowhere that you can set the error correction level in Affinity programs. Eyeballing the codes I would expect it to be (L)ow. Maybe something for a future enhancement?

I think that is right from my playing earlier. Maybe there is no way to send the DPI info via the clipboard so it defaults to 96. For some reason I broke with my normal workflow which would be to save a copy and delete extraneous content, that way the document, dimensions, colour space, margins, guides etc. are retained plus of course, the DPI. Lesson learned!

Spot on @walt.farrell - the original was 300dpi the new one 96 dpi. I can't for the life of me see any logic there. This is Designer and the content is vector where DPI is academic for most work. I could see that perhaps pasting a copy into another document with a different DPI might require a resize but not when creating a new document. The printer thinks I'm losing it! 🤣 Thanks Walt.

It is weird that this has just started happening - twice in one day. It seems that the clipboard is not retaining the original dimensions. I have a large design and the printer has just asked for an element to be broken out so that it can be made as sticker as positioning on the final background may need to change. I copy the outline element which is ~1400mm wide and then using Create new from clipboard I see that the dimensions are over 5000mm. The exported PDF gives the above error as you might expect. The background graphic (which houses a hidden group with the outline element) exports fine and at the correct scale. Any idea why this is happening and what I can do to prevent it in future? Is it something to do with Scale with object?

I wonder if a customisation in a previous version, via View > Customize Tools... as @R C-R mentioned, means that this is not visible by default as it wasn't included in the custom set of tools shown when the update goes through.

Hi Tony, it is at the end of the shape tools on my install: As far as I know this is bundled with 2.5 and there is no way to enable or disable it so it should be visible. Maybe try a shortcut to see if that triggers it like I've done with 'Q' here:

I had a job a little while ago which use a proprietary font and the client (who owned the rights) could no longer find the font file to share with me so that I could update the designs. It is pretty frustrating when Adobe Reader displays it and the customer doesn't really understand why you can access it. In this case I ended up using FontForge to extract the font file from the PDF and then I could install it and use it to develop the design. This time the complete font was present. Usually you only see the used subset of the font and it isn't much use unless you are only wanting a few characters. I know there are a couple of other programs out there that do a similar job. Good luck.

It depends on the result you are aiming for. For a quick scale-to-fit-the-page-print I normally select everything, Copy and then use New from Clipboard and then print that using the Scale to fit option in my print dialog. For real scale I use Actual size (I think - I'm not at my workstation atm) in the print dialog. The thing that can defeat this method is when you have a rotated object and the bounding box is also rotated so corners extend the selection beyond the visible content edges. In that case you need to fix the bounding box issue by using full stop and then Ctrl+full stop IIRC. This is all from memory so apologies if it is not complete are completely accurate.

Hey, @firstdefence, thanks for going to all this trouble. That's interesting what you have found. I think in my case the gradients are part of the final output file as there is a distinct colour change between the original and the AD import. I appreciate the effort that you have gone to but I don't think this is worth taking any further on my behalf though. Cheers.

Thanks @firstdefence I did search but saw nothing quite like this. I guessed that it would be something that Affinity hasn't catered for in its processing of PSDs. I'm not confident about receiving a more compatible file so I'm exploring ways forward. I'm thinking that as the process is going to print (and the source is RGB) that I can hide/explain some of the colour shifts down to the CMYK conversion but I might have to eyeball some tweaks so that it's still "within acceptable parameters"! 😊

Hi everyone Before you tell me what this means - I know! I'm working downstream of an agency who care little about me or Affinity Product compatibility. The "source files" they sent on which to base my work were all IDMLs with linked PSDs. I need to incorporate them into a new design and some of the colours are way off - I presume because of the errors thrown up when the import is done. Does anyone know what in PS these relate to? I'm hoping that someone can flatten or bake the effects in a manner that will not cause a problem by the time it reaches me. i.e. I need to write a request in detail but I've no idea what the correct terminology should be. I asked for a PDF but I ended up with a file that was rasterised down to a handful of layers - so I think I need to spell out things in more detail. (It is a long time since I used PS).