maybe folks can get used to monochrome traffic lights as well. why bother with red, yellow, and green.
"why colour matters in user interfaces " Ask Riston, or better yet, someone who cares
You just got on my "blocked user list" as I can't get used to monochrome brains.
I still have version 2.6 installed on my Windows computer and I opened it this morning. Icons are set in color on this computer. Well, I prefer the monochrome icons now. To me, the color icons give an old software look to the app.
Since I arranged all my studios tools to my liking I feel comfortable with all of them. I would not go back to color icons. But I can understand that some people miss those color icons. I don't understand why the option to allow users to choose what they like has beed removed. There must be a hidden switch somewhere.....
All three apps work fine on iPad with OS 26.
The problem is that Monotype bought FontSmith. So, if you want to buy these fonts outside of Affinity, you're stuck with Monotype's ridiculous licenses that make you basically pay a subscription on these fonts if you embed them in a commercial PDF. If you stay inside Affinity and use them, then you can embed to your heart's content with no additional licensing fees. I confirmed this with Affinity support. So, if you're making PDFs for yourself or a client that needs these embedded in a PDF, these are a good deal.
When these fonts are embedded in a PDF only the characters used will be included. For example: If the phrase "No Thank you" use theses fonts, only those characters will be embedded and there is no way to edit the text outside of Affinity.
A few days after v3 came out I disabled it. Two days later I missed it, so I re-enabled it. All the jobs I'm working on at first glance when I open the app, I appreciate this opening screen. But I will try to delete all those "Learn" documents under "Welcome to Affinity".
This almost certainly is because the licensing terms prohibit embedding the entire font in exported documents, so if you try to use any character not in the PDF to begin with, you would get that warning.
This is exactly what happens. Disabling fonts is quick and easy. Over the years, I have acquired thousands of fonts, both free and paid, so I should be fine.
I deactivated all those free fonts. I created a document using some of them and exported it in PDF format. Now when I try to edit the text with a PDF editor I often get the message that some characters are not included is this font and may be lost.
I know it won't matter to most people, but I don't want to take any chance, so I will not use them anymore.
I used one this week for a job, a logo. But, as mentioned above, they are OK. I could I have use another font as well. I did not activate all of them. I like that they support French language accented letters that I need very often. So many other fonts don't. And... it's free.
... Why do I feel like I'm gonna quit this forum soon?
Your forum ‘sig’ only mentions Windows 11. Which versions of iPadOS and macOS do you have?
I'm sorry. I don't use Affinity anymore on my Windows computer.
When you performed your original Windows v3 installation Alain, did you use the Affinity x64.msix file?
I'm on Mac OS
I noticed that a few days ago, but I like the new way it now works.
BTW, Old Bruce is not a real person. It's a AI robot that has the answer to all your questions regarding Affinity.
In the app you ask Ritson, on this forum you ask Old Bruce.
Sorry for the late answer vkbellis, I also downloaded the app from the site and updated manually.
The page is available in French (https://www.affinity.studio/fr_fr/blog/fcr) but the fonts still don't appear in the list in the app yet.
I opened a RAW file and moved the panels to the second screen. Clicked Develop and then closed Affinity.
Next I selected a RAW file and Open with Affinity Studio. It opened in the Develop Studio and all my panels were still on the second screen. It just saved the panels setup automatically. This is on Mac.
Right click on the Studio you want on your second monitor and select "Update... the name of your Studio". I recommend creating your own.
Here is what I get when I click on the "Question mark" button on Mac.
Could be too many people updating at the same time but all I get is an error message with a "try again later". That's is what I'll do....
Following the steps above I don't have any crash on MacOS 26.1 even without closing the quick export panel.
It looks like a Windows problem as it works fine here too on Mac.
