Search the Community

When creating a keyboard shortcut, if I enter in a shortcut that is already in use (and surfaces a yellow warning triangle), it would be nice if Affinity showed me right there which tool/menu is already assigned to that shortcut and gave me a chance to override it and remove/change the other one. As it stands now, I have to search through all the menus to figure out what tool/option already has the keyboard shortcut I want to use.

To be completely honest, I am a font hoarder but I AM DETERMINED to purge and organize my "font" life. I know I am not the only person in this world with this problem, so I'm asking for help for all of us who have too many fonts on our computers. Now, just so you know, I download fonts and keep them organized in folders titled by the Author's name. Now, I'm organizing those fonts into folders with appropriately named font type categories. (PLEASE SEE THE ATTACHMENT - it is a work in progress.) In some of the folders that you see on the screen capture, I have created sub-folders, for example: Serif_Classic a - Font Family b - Single Weight c - Multiple Weights d - Extended e - Contemporary_Modern f - Slab_Square g - Soft Round & Partial Round Terminals h - Condensed_Bold_Heavy_Black i - Unique To achieve my font organizing goals I am using FontBase. In FontBase I organize my fonts by: 1. Adding an author's folder. 2. Placing fonts from the author's folder into an appropriately named collection folder. 3. I then zip up the collection folder and export it to my document's folder. Here is my ask... The font "Favorites" folder has been very helpful but for a "font hoarder" it's not enough. One of my favorite features in Affinity is organizing graphics into ASSET folders. Would there be any way to add "LINKED FONT FOLDERS" to the Affinity ecosystem? I can organize my "font" life all day long but I turn into a mess again when I can't keep my fonts truly organized by "categories & collections" in the software. Oh my. I can't believe I have made this confession on a public forum. If you are a font hoarder, please commit below so I don't feel ashamed and alone here. Thank you for your support and understanding. Angela

This should've been in the previous release but here it is again. Markdown import so we don't have to convert to legacy formats or use crude copy & paste for each article. Solution: Link Markdown files to text frames like the data merge preview. That way the documents can be worked on by writers/editors and kept up-to-date via the Resource Manager.

These were reports in the past few days, here in the forums, since 17 became officially available.

Hi @MikeTO thanks for pointing this out! I do think though, that your reply belongs to this thread: What I am asking for here, is additional functionality for the sidenote tool to allow me to place sidenotes in a frame alongside the text frame with custom paragraph style formatting. In addition, I would like the sidenotes not to be aligned with the text, but rather fill the frame alongside the text from top to bottom. Right now, the sidenotes are always horizontally aligned with the position they were inserted in the text. See: 2023-09-24 16-36-49.mp4 But using cross-references for sidenotes has the disadvantage that the notes have to manually be added to the correct text frame on the correct page. Hope this makes sense.

I was thinking about the context toolbar in v2 again and I wanted to give another reason why its bad to have it at the top. In Affinity Designer v2 for the DESKTOP app, the reason why the context toolbar works at the top of the UI is because you dont have a hand holding a pencil covering the artwork when you make control changes. You have a tiny little mouse that doesnt cover the artwork when you make control changes so it works there on the desktop app. But it doesnt work when you put the context toolbar at the top of the UI in the ipad app because you have a hand holding a pencil cover your artwork so you cant see the control changes youre making. So this is why I say that theres 2 different devices with 2 different tools. A mouse and a hand holding a pencil. You gotta design the UI with those tools in mind. You cant just design the ipad app like the desktop app and say, "oh. if the desktop app has the context toolbar at the top of the UI then it should be like that in the ipad app." No. it souldnt. -------- I was also thinking about sliders. Sliders are for when you have a min input and a max input. Min being 0 and max being 100. It depends on what max input you want the slider to have. Its usually 0 to 100. Think of the opacity slider and the stroke slider. Or your brush might have a max brush size of 2000 px. Lets just say that so the slider would go from 0 to 2000. So the sliders is registered to go from 0 to 2000 and if your finger is at the top of the slider youre at 2000 px. You cant use your finger to slide beyond the slider. The top of the slider stops at 2000 px. The issue is some FX controls dont have a max input. The max input can keep going and going. Thats where I think its weird because the max input on a slider should fill up until it reaches the top of the slider because thats the max slider input. You shouldn't be able to swipe beyond that because you reached the top of the slider. That slider only goes from 0 to 100 or 0 to 2000. So some sliders let you slide beyond the slider and this is an issue because when you increase your control input by swiping up on the slider and you've reached the top of the screen of the ipad you've hit the max input of that slider. You cant swipe any further up to increase it. So if you wanted to keep increasing your max control input you cant. You would think you could go back down to your slider, tap, and swipe up more to increase your slider control input but it just takes your slider down to a lower input. so increasing your slider only decreases your slider and this is why I hate sliders for controls. Each slider already has a max input depending on where they're positioned on the left side of the UI. top sliders have less space to swipe up. bottom sliders have more room to swipe up. check out the video below. the top slider goes from 0 to 100 which is correct. the middle slider however goes beyond the slider. which is weird because sliders should only have a min and max input. not go beyond the max input. but pay attention to my touch. the little blue circle. as I increase it all the way up i hit the max input at the top of the ipad screen which is 340. if I wanted to increase it even more i cant because i dont have more ipad screen to keep swiping up. so you would think you would go back down to your slider and swipe up more to increase your input but no. it just decreases your input. so theres no way to increase your input because of the limited iPad screen. if you want to increase your input you have to type it in manually. you cant just keep swiping up because youve hit the max input and swiping up more only decreases your input. you cant even swip right to increase it more. the bottom slider has a max input of 502. if I want to go beyond 502 i would swipe up again but swiping up only decreases my input so i have to manually type in 1000. sigh. RPReplay_Final1695481190.mov

I personally don't think that a multiplication or a division are too difficult tasks, even for creative people, but you don't need it anyway: You should only set your document (File > Document settings) @ desired resolution and set its dimensions in whatever unit you like. All maths are done for you there. It has, implicitly. As explained before by @Old Bruce, when you export in TIFF, it will be presented in pixels, as this is the only pertinent unit for a digital image, but rest assured that when printed at defined resolution (i.e. say 300 ppi) it will have the right dimensions (wether you use inches, meters or feet). (The same way, when you export in PDF, you only see the resolution chosen, no pixels nor inches or cm.) If you want to resize your document at export time, blindlessly on last minute, you can also introduce directly a percentage value in width field, e.g. 120% — but this resampling will therefore modify resolution or dimension(s), as we all know. I admit that in this case a visualization in the export window of [the resulting dimensions for any given resolution], or reversely, could be useful – but that's apparently not the place chosen in the interface to do it. In none of the Export options (PDF, EPS, JPEG…) you have dimensions. Only resolution OR pixels. At least, you can type it yourself, as explained above (pixels = inches * ppi). That's the reason I sometimes use this spreadsheet aside, but it won't perhaps be very practical to include it in the export window…

Hi Mike, Here's the problem illustrated in a video: 2023-09-24 10-14-00.mp4 I don't know of a way to reproduce this kind of sidenotes using the built-in tools (to automate the placement of sources and notes using this format). Please have a look at this file to see if you know of any. Sidenotes with cross-references.afpub

It's easy to search notes, just not see them all at once. To be able to search notes, apply a paragraph style with Note Body Style. Then search for that paragraph style with Find and Replace. I do that regularly but I have to click each search result to see the entire note. For your need, I'd suggest my original suggestion which is to convert all footnotes to endnotes, using a temporary copy of the document of course. Then you could review that consolidated list and switch back to the working copy of your document to fix any inconsistencies. Good luck.

I did some experimenting and here is what I found out using AP V2.2 1.The paint brushes and smudge tool perform just as expected on a new canvas with two layers... the first layer a solid color with brush activity on the second layer... there is no hesitation with either the paint or smudge tools. ....afphoto size = 5.6 MB Megapixels=28.8.. Document size 16"x20" @300 DPI 2. Hesitation and choppy application of color and blending with the paint and smudge tools on the file in question with 17 layers which include gradient maps and grouped layers. I didn't have any issues with this same file when I was running AP V2.1.? ( whatever the last version before the upgrade to V2.2.) The afphoto file size is 119.6 MB and 34.56MP. Document size 18"x21" @ 300 DPI Actually, I had a few more layers with this file while using V2.1 without any difficulty.... but deleted these layers to the existing total of 17 layers. 3. Copied the one layer containing a main character along with two background layers for a total of three layers to a new file and the brush and smudge tool performance is better but still has some hesitation but not as bad as the larger file which is having the issues. Afphoto file size is 44.2MB and 28.8 MP. Document size 16"x20" @300 DPI Just a non-professional guess, but it looks to me as a AP memory issue, how AP is allocating its resources. Again another non-professional guess, could it be that AP is holding on to some file memory , even when layers are being deleted and AP is closed out ( to erase all history) and then reopened? I am running the latest Mac os, Ventura 13.5.2, with a quad core intel i7, with graphics Radeon Pro 580 8 GB, and 64 GB of 2400 MHz DDR4 ram. I have AP V2.2 performance Ram usage limit set to 60416 MB Your thoughts are appreciated.

What should this be, some feedback or a suggestion? - However it's no resource in the sense of this forum section here and so probably it belongs and is better moved to the Feedback & Suggestions forum section.

Thanks for providing this link in this thread. I have downloaded your book. Though, I haven't had time to read it yet. It looks pretty nice so far.

I'd love to be able to view a list of all my Notes in the static left column just like I can for Indexes, and have a quick way to search through Notes and show all the matching Notes. This would be very useful for reviewing Notes, making sure multiple notes don't cover the same thing, etc. Like an Index I'd like to be able to click on a Note, and have it jump to the page it's on so I can see it in context. It would also be useful to be able to double-click on the note marker and if the Notes column is showing, have it jump to that note in the list as well.

I'm writing a novel currently, using Markdown as my writing format; I want to produce text right now, I don't want to deal with formatting beyond declaring that something's italicized, bolded, whatever. When it comes to page layout, however, while I'm familiar with LaTeX and wouldn't be opposed to exporting to that and using it to generate PDFs, I was hoping to use Publisher, since I've enjoyed Designer so much. Lacking direct Markdown import means I'd need to export first to Word, then import; this also would break my flow for edits, since my root text is always going to be the Markdown. Part of the goal here is to retain the structural clarity that markdown provides, and the simplicity of working with it, while getting the control of a proper publishing suite.

Hi, I can't duplicate this issue, it works for me. I created footnotes in one chapter and then created cross-references in another chapter. I selected Note Number from the Text field's menu in Cross-References to insert the footnote number. I tried it with paragraph and anchor and both worked fine. It's best to insert the anchors at the start of the note or paragraph but I also tested it with an anchor in the middle of the paragraph, too. Here's a test doc (not a book chapter) showing how to do it. The first CR targets the footnote paragraph (which created an automatic anchor at the start of the note) and I chose Note Number from the Text field's menu. The second CR targets the first anchor I created which I manually added to the start of the note and the third CR targets the second anchor I added on the second page of the note since this note was split across pages as you said you sometimes have to do. Everything worked great for me. Does this document work for you? Open it and update CRs to ensure it's all working correctly. test.afpub

You might like Typst and since Pandoc 3.1.2 there's a path from Markdown to Typst. It's a bit easier for hired editors to work in because of the browser based UI. The template language has CSS ideas as its base. Affinity probably plans to do what Amazon does "…we're seeing an increase in requests for Markdown support. … In the meantime you can use the export function of your Markdown editor to create Microsoft Word compatible files…" Basically try to wait it out for several years like Microsoft did with the Internet.

And now, of course, it's working as expected, even with my document. Sigh. No idea why it didn't work before, since there is nothing special about Paragraph references. Until you explained the above, I didn't realize that choosing a paragraph is just a shortcut for creating an anchor. Thank you for your help.

I just wanted to add another reason for this feature – consistency checking. It would be very useful to be able to search for a word, see the matching footnotes, and check for consistency. For example, when quoting from a source, am I formatting my quotes in the same way? Also, if I have an explanatory note about a person mentioned in the book, I may have written a similar note later in the book if the person shows up again. Being able to search notes, and see the matches, would be very helpful for preventing this.

Hi, I enjoy of this V2 Affinity suite. I think it could be useful to create a widget ( mini application) for Mac and PC to get a notification of new versions and allow user to uploads each app or all together of Affinity suite without open each Apps. This would save time and avoid waiting for applications to be downloaded and installed . It could also allow user to manage default parameters, downloaded or futur Add-ons and display a library of all Affinity tutorials with a search function and show YouTube video inside your App. This one must operate independently of publisher, Designer and Photo. Thanks for your work.

such a waste of time if you work with different aspect ration presets. the only workaround I can think of is to create a folder, fill it with blank *.afphoto files at the resolutions and orientations you want. Then make a copy of the one you want before opening it to start your work. What they've built now is simply incompetent.

I bought Affinity Designer v2 for the iPad back when it was launched in 2022. Since then I have NOT been able to use the app because someone at Serif made the bad, BAD design decision to redesign the context controls for tools and effects on the iPad and the app is unusable. It upsets me so much because I BADLY want to use AD v2 on the iPad. I bought it! I want to try out all the new features it has, but I can’t because it's just unusable with this new context control design. It is REALLY bad design. Let me explain. The context control design in AD v1 on the iPad was perfect. Please see the photo below titled "ad v1 context." It had everything I needed. It was a little rectangle box that told me, in text, what each button and dial does. It is so easy to understand and its the ONLY reason why I use AD v1 on the iPad. This context control is just so well designed. Its so well designed that even Procreate, the number 1 art app in the App Store, uses the same design for their app. Please see the photo below titled "procreate context." Someone at serif made the bad design decision to take this perfectly designed context control, split it in half, take one half and add it to the left as sliders, take the other half and move it to the top, remove all the helpful text that helps tell users what each button and control does, and then created these unrecognizable biohazard looking icons that users are now supposed to guess what each icon is and what each control does and its just SO bad. Its so, so badly designed. This was not supposed to happen in v2. The context control was supposed to stay the same as in v1. No one said to redesign this perfectly designed context control into a new bad design context control. It really is bad. You just can’t design it this way. Please see the photo below titled, "new v2 context." Look at how there are now sliders with icons underneath and icons at the top. There is no helpful text to tell users what each slider or button does. And before you tell me to hit the "helpful" icon on the bottom right corner of the app to figure out what these sliders and buttons do, please know that if I have to do that then that's also bad design because the developers and designers for the app couldn't tell me what a basic slider and basic button do because they removed the helpful text. You can’t create new icons for basic controls and then expect users to know what these newly designed icons mean. You just can’t. Please look at the photo below titled "new icons." Theyre not universally designed easy to recognize and identify icons for users to understand what you mean, serif. You need to just tell us, in text, what the controls do. You dont need icons. You just need text. Tell me this control changes my stroke and opacity. Don’t design an icon that makes me guess what this control does. Thats where the bad design starts. You need to just tell me, in text, what the control does. Thats why the context control in v1 was perfect. It told users what each control does in text. Please look at the photo below titled "new icons." You just cant tell me that im supposed to know what these 5 icons mean. You cant! I'd probably only know the opacity icon in the middle and then rotate and brightness for the other 2 after. It turns out that the icons from left to right mean offset, radius, opacity, angle, and intensity. NO WAY, NO WAY was I supposed to guess right that these icons meant offset, radius, and intensity. NO WAY!!!! Thats insane!! Thats insane that you think users are going to guess what these icons mean and are supposed to work this way. Its insane that Im supposed to figure out what these icons mean. This is why its bad design. Just tell users, in text, that these sliders mean offset, radius, opacity, angle, and intensity. Its that easy. Another reason why this new context control is bad is because you have other controls hiding inside sliders. Please dont EVER do that. Dont EVER hide a control within another slider. That is such bad design. Its so bad. You can not tell me that I'm supposed to figure out that a control that i needed is hiding inside a slider and the way to get to that control is to tap the little circle icon above the icon to toggle into it. Thats insane. You can not justify that. Thats bad. You dont toggle sliders. A slider is meant for 1 control. You dont put 2 controls in 1 slider because you wanted to save UI space. You also dont tell users that you need to tap this little white circle to toggle into the other slider. Its just BAD, BAD, BAD design. Its so bad I'm overwhelmed. Please look at the photo below titled "toggle." I shouldnt be tapping this little circle icon to get to other controls. Just display my control as a dial, how you did in v1, and put text underneath it so that I know what I'm controlling. Please look at the photo below titled "ad v1 context." There are dials with text underneath that tell you what each control does. No sliders. No controls within slider or dial. Each dial controls 1 control. Thats it. simple and easy to understand. Theres so many other reasons why this newly designed context control in v2 is bad. I can list you 5 or more other reason but its so exhausting to explain it all in type here. Its so exhausting. I’m stuck using AD v1 on the iPad. I hate it. I want to enjoy all the new features that serif has introduced in AD v2, and I can’t because this new context control makes the app unusable. I need the old design of the context control back to work, so I have to continue using AD v1. It upsets me because this old context control design will never come back. Not now. Maybe never. I really need serif to fix this issue. Bring back the old context control. I don’t know why it was changed but please know that this new context control in v2 is bad design. Very bad. ad v1 context procreate context new v2 context new icons toggle

Another suggestion here for implementation here is to add a preview colour. When adjusting the curve, the preview colour lets you see what areas are being affected, rather than guessing …..this preview colour could be turned on or off as well.

There's been a longstanding request in the Publisher v1 forum to add GREP into Text styles. I was excited to see the announcement about v2 but saddened to see this didn't make it in. Since the feature isn't there (yet? ) and since those v1 forums are being archived, I'm bringing the request into this new forum to keep it alive. For a specific kind of technical document I work with, there are dozens of types of replacements that need to happen on the text in new docs, within one text style. Having the GREP expressions in the style definition makes all of these replacements happen in one click of applying a style, rather than a laborious effort to do them individually. I understand that this isn't a mainstream feature, but it's so, so helpful to those that need it. Since the engine is already in the software, it seems like it shouldn't be a huge deal to be able to attach GREP search/replace expressions into a text style. I could be wrong, of course, as I'm not a developer. But I (and many others) would very much appreciate this coming in a new update.

Oh yeah, this is great news for me and I wasn't aware of that. But it is also a bit tricky to find out, so here's the solution for anyone else having this issue: Open the Export dialog Make your adjustments for size, format and compression Now this is the tricky part: you might have to get the keyboard focus away from the input fields. Sometimes just hitting TAB works but normally this only skips to the following input fields. What works for me is collapsing and re-expanding the "File Settings" section or scrolling down past all the controls and click in the empty area below "Embed metadata". THEN you can indeed use CMD-1, CMD-2 (not on the numpad) and so on to control the size of the preview. In case I missed an easier solution please let me know. Otherwise, the Dev-Team could make this a bit easier to achive on macOS. But nevertheless, thank you for your help! 8-)

Now, I know what youre probably also thinking. Why not use your left hand's thumb to change the sliders? Why not have your right hand holding a pencil and your left hand to change the sliders? Because its still bad design. Theres many reasons why its still bad design. The hand covers the artwork when the context toolbar is at the top. You still have controls hiding within sliders. Thats bad. This isnt hide and go seek. You still have controls that cant be translated into icons. You need to spell them out. Your left thumb can only go so far down and up. Having your thumb go all the way down and all the way up of the ipad screen is crazy. The left thumb is supposed to be centered in the middle and it can only go up and down a certain distance. Wacom doesnt put 3 sliders onto their wacom tablets because they know the users thumb can only go so far up and down. 3 sliders is crazy. Even crazier to hide 4 controls into 1 slider and have 12 controls hiding inside 3 sliders. Like theres so many reasons. You cant turn controls into sliders. You cant. Theres too many controls. Theres so many controls that serif tries to fit 4 controls into 1 slider. Like, thats so bad. Theyre better off as their own dial like in ad v1. The only reason Procreate is allowed to have 2 sliders on their UI is because Procreate is a drawing/painting app. You select a brush and that brush has 2 controls. A brush size control and an opacity/flow control. 2 controls, 2 sliders. These sliders have to be displayed because these controls are always being changed when drawing and painting. Unless procreate intoduce a gesture to change the brush size and opacity/flow like the ipad app infinite painter does but affinity has too many controls to fit them all into sliders. It doesnt work. You cant be playing hide and go seek with users.