Gabe

Thanks. We will have a look

That fix was for a specific font. We would need your font to see what's going on. https://www.dropbox.com/request/zdVo7oYjP6thLwqScPvq

I'm afraid that is expected. You cannot open 2.6 files in 2.5

@Iztokplease use the regular forums for these sort of questions. The beta section is for beta specific issues. If you are just using the beta to learn the app, this section it's probably not the best place. You would be better off using the retail version for this sort of stuff, and asking any questions about how features/tools work in the support zone > https://forum.affinity.serif.com/index.php?/forum/3-affinity-support/. Thanks.

I'm afraid I don't know. Sorry.

If you type * in the File name field and press return it will bypass the filter and show all documents/file types

Not really. It filters out unsupported extensions/file formats by default. You have to manually change it to * to accept unsupported files, which is why is not documented.

The lens profile was added to the repo 3 days after we released. I'm not sure when it will be another pull from that database, but we will update the list when it does happen.

That's expected. It's not meant to work with AF files.

Can you both use this link to upload your files please? https://www.dropbox.com/request/VG5V0Mn5ADOFK7SBX6MN

Duplicate of

You are trying to apply that text style to a group and not a text frame. Try to apply it to the frame and it should work.

Can you please attach a screen recording of your entire screen with the colour panel visible to understand what's going on? Also, another video for the stroke value being different please.

There you go https://www.dropbox.com/request/OqVaP3Y02xv6U2wWahjH

Is this crash reproducible?

Please create a new post as this most likely unrelated. https://forum.affinity.serif.com/index.php?/forum/5-affinity-on-desktop-questions-macos-and-windows/

I'm not seeing that on my end. Where did you install your font from?

It looks like it, yes. The size is no longer 1.26, but 379kb

Hi @blondie63, Thanks. We are aware of this issue. I'm afraid there is not a workaround at the moment.

This has now been fixed. Thanks.

The font in question (Frutiger) appears fixed. If you attach a few others that are broken, we can have a look.

Can you please attach the file so we can log it?

Thanks. We are aware of this issue.

As far as I'm aware, we will not be adding the logo "feature". This is not something that is part of the QR code spec, and having a valid QR code with a logo in the middle simply relies on the error correction to account for the "covered" pixels. I think a middle ground would be to expose the error correction levels and let those who want a logo experiment with its size and error correction levels until they find settings that work for them.

What happens when you tap on it?