dominik

Just to be clear on my side. I absolutely do not oppose the request for a font manager. This is what this forum is about. I just do not see it coming soon and that why I offered my workflow as a solution. Cheers, d.

I did not say that it is the same nor as good. I doubt we will see a font manager by Affinity in the near future. That's why I chimed in to present a workable solution (at least for me 😉 ) d.

As others already stated Main Type doesn't do this. I am using Main Type Pro myself and get along with it quite well. How I do it is to create project groups that contain all the fonts used with a special project. Those groups and the fonts in it are just links they do not take up much space. That way I can activate all fonts that are associated with a project with one click. It's not automatic but not bad at all. d.

This sounds like a bug to me. d.

Regular expressions seemed to me alway like a book with seven seals. Now I know why 😉 Impressive! d.

Hello @Sleepy Panda, welcome to the forum. Look for 'Sculpt Mode' (icon on the toolbar) and turn it on. It lets you reshape a path. To close a path you have to switch to the Node Tool. This does not work automatically, yet. d.

Hello @nitsuj817, I did not know what a GRD file is, so I looked it up. There seem to be more than one GRD file format (e.g. Adobe Gradient file and some kind of Grid files related to 3D software). It would be good if you could be more specific on what you are looking for. For sure I can tell that GRD files are not supported by AD or APh. At any rate you have to use some external software/utility to do the convertion into a format that is supported by them. You can see a list of supported file formats on this page (under 'Professional Colour, Compatibility, and Output' down the page): https://affinity.serif.com/en-gb/designer/full-feature-list/ Cheers, d.

Hello @Rawshooter6 and welcome to the forum. I don't think it is wrong to ask for support of the old .BMP format but I think it is of low priority on their to do list. I say this because convertion from Affinity's supported formats to .BMP can be solved easily and even automatic. I think it would be better to use a working solution now than to wait until it is implemented by Serif. Example: the free to use (for non commercial work) XnConvert (https://www.xnview.com/en/xnconvert/) converts many different image formats to .BMP. And it can do this even automatically. Quote: 'Watch folders for new or updated images and automatically apply a custom set of edits.' Cheers, d.

I can confirm this. d.

Hello @vaidab and welcome to the forum. This is exactly what I was referring to with my above posting: Quote: "Apart from that it is possible to place text left and right of a spread that could be used with some discriptive names." This would look something like this: You don't need page names to get this done 🙂 d.

I was just looking up the very same post just to see you beat me to the minute 🙂 Nothing more to add. d.

I think this is another separation line being drawn between APub and AD. Pages are numbered and artboards can be named. Apart from that it is possible to place text left and right of a spread that could be used with some discriptive names. Not much more effort than typing in a name in the spread properties. The only drawback: this text is not visible in the Pages Panel. d.

Glad to be of help. For pages you have to work with Affinity Publisher (if you have it). It was discussed here several times to have pages in AD, as well. Opinions about this are mixed. I do not miss them in AD. Cheers, d.

Excuse me, this is the definition of global colours. If you want to have global colours that are restricted to just one artboard you have to adapt your workflow. You can define the same colour multiple times and e.g. call them 'corporate red artboard 1' and 'corporate red artboard 2'. That way you can change them seperately for each artboard for multiple objects. Cheers, d.

Perhaps I was not clear in my other posting. I am not saying that there should be no distinction between regular number keys and the numbers on the numpad. I would highly like to be able to assign shortcuts to these (and do this in other programs I use). I just wanted to point out that if some shortcuts could only be assigned to numpad keys then this would leave out many users with out a numpad. I think, basically we agree that a very variable way of assigning shortcuts to as many input devices as possible would be of benefit. d.

Hello @Manege, in the mean time I played a little with a short document consiting of three documents that were merged together. I especially was interested how a table of content might work and it did. With a little planning (text styles) this could work as a very basic book feature. But I would not consider this as a serious solution for now. I'd rather stick with one long book file until this is implemented properly. d.

While I personally like the num pad very much (since my keyboard has one), we have to keep in mind that there are many computers out there that don't have a number keypad. A restriction of certain shortcuts to just these keys would cause much less flexibility 😮 d.

No. d.

I do it in a similar way with language setting. The release version is in my native German. Betas are in English to easily quote UI elements when reporting here. Of course this won't work for some of you. d.

What I try to say is not that we should not provide feedback. What I try to say that I do not think there is a 'fool proof' way to solve the problem to keep the beta version and the release version visually apart. It takes us users to also make that distinction. Cheers, d.

Hi @Angus Kennedy, this happens constantly. E.g. just recently a template feature was introduced to the currrent beta versions (it was on Mac in the test loop for a little longer but showed up on Windows just this week). Just one of many threads on this topic. Same for improvement of 'Expand Stroke'. This is a feature discussed over years and now they have made big improvements ... they are ironing out some last bugs. Another thing that comes to mind is export to TGA format. It was asked over and over again and the developers did listen and implemented it. Interesting thing in the last post by Andy Somerfield is that they found valid arguments in the postings in the forum that made them to decide to implement TGA support. They do listen to the people around here! Since you are new to the forum I just wanted to point you to these few of many examples that are proof to the fact that Serif is monitoring these forums. Cheers, d.

I agree with you in this in regard to release versions of the software. But as we both are actively using beta versions I think there is a liitle difference. We, as beta testers, cannot ask for a fool proof seperation by the developers of release and beta versions. This needs some participation and commitment by the beta testers, too. This is why I developed the habit of very closely looking at what version of Affinity I am using. I am not against your proposal to emphasise the status of a beta version. But I think this is not going to prevent accidential edits. Cheers, d.

Since you are asking. I am very able to do things accidentially and mess things up. But with Affinity I developed the habit to very closely look at with which version I'm working. I doubt any kind of extra display will help here. Once your 'in the heat of work' you (and me) most likely miss that. It's really better to actively distinguish between the versions. My way is the following. Release apps are fixed to Windows taskbar. The beta versions are just icons on the desktop. I also do not double click on an Affinity file. I always choose 'Open with...' from the right click menu. That way I trained myself to always spend a though on what I'm going to do next. d.

I posted my observation over in the APub beta forum and this is the reply: We can look forward to improvement 🙂 d.

I'm sorry to hear that you feel some dissapointment. But I want to point out that you also have to think about your planning. This should have brought to your attention that this feature is missing in the first place. d.