NathanC

Hi @David Tee, Global colours might be what you're looking for, these are created in the swatches panel, when global colours are edited they simultaneously affect all objects with that colour applied, the help guide linked below gives a detailed explanation of how they work. https://affinity.help/designer2/English.lproj/pages/Clr/globalClr.html Edit: This only works on the basis that your buttons are vector objects with fills 🙂

Hi @LCamachoDesign, This is a known issue that's currently logged with the developers, the Picture frame hit/drop zone is not correct, making it incredibly difficult to correctly position them in the stack via drag and drop. I've now bumped the existing issue with your report. 🙂

Welcome to the forums @Vagn Majland, It's worth noting that Addons and Plugins are completely separate from one another, plugins are 3rd party apps installed externally and then linked with the application. The location of your installed Addons really depends on what it's contents are. For example in your recording you have the Paper Farms overlays installed, these can all be found in the 'Assets' panel (Window > Assets) and then changing the dropdown to access the different addons. Another example is a Brush pack, this can be found in the Brushes panel dropdown menu. There are many other types of addon packs accessible from other panels within the app. I've linked the resources install guide for more information on different types of asset packs and where they can be found within the apps once installed. https://affinity.serif.com/en-gb/store/resources-install-guide/ Also, under 'My Account' clicking on the dropdown arrow to the left of the addon will give you more detail on what type of content the addon pack contains, along with a user guide which provides further instructions if required. I hope this helps!

Welcome to the forums @Beardeddabber, I don't have an iPad to hand currently to check for comparison, but after merging all 5 of your RAW images using the default settings and without tone mapping I'm left with a generally well exposed outside and no blurriness when compared to a single RAW at the same zoom value (200%), this was with the HDR/32bit preview enabled which is available on my monitor, with the HDR preview turned off the outside highlights would be immediately clipped similar to what's shown on your final result, however. If I instead opt to tone map following the HDR merge, clamp to SDR and then set the tonal compression to 100% I'm left with the below result. In your previous merges, have you been tone mapping the image, or is tone mapping something you want to intentionally avoid on your workflow? https://affinity.help/photo2ipad/English.lproj/pages/HDR/hdr_tonemapping.html

Hi @drkanukie, I also am not having any issues editing the table borders on your page after detaching the master, I can freely select which border I want to edit and then change the stroke properties etc. In this scenario it would be good if you could provide us with a screen recording demonstrating what's happening when you're trying to edit the table borders on the page after detaching the master. Many thanks!

Hi @Smartweb, As Red Sands has indicated the inability to embed an ICC profile when exporting to Webp is an issue that has been previously logged with the developers, i've now bumped the existing issue with your report, hopefully it will be fixed soon but sadly I don't have any news to share on it currently. This thread has been tagged with the issue so once it has been resolved the thread will automatically be updated.

Hi @bbrother, Are you looking for TOC formatting like the below? It looks like the initial tab stop issues are caused by the text style being used for the TOC having numbering applied via Bullets & Numbering and there only being one initial tab stop for the TOC style. To correct the tabs after inserting the TOC in the Text styles panel I edited the 'TOC1: HR_Nr' style and in the Tab Stops section I deleted the initial tab stop and then re-inserted a left aligned tab stop at 10mm for the tab stop between initial number and header, and then added an additional right aligned tab stop at 160mm for the page number. The same can be repeated for the second 'H2_Nr' style but I gave it a left indent and different initial tab stop value to better differentiate it from the first headers. TOC.afpub

Hi @Bryce, Thanks for following up with your sample file and recording, this definitely looks like a regression over 2.0.4, I've now replicated and logged this with the developers.

Welcome to the forums @AdamF, I've replicated and logged this with the developers, many thanks!

Hi @BBG3, Thanks for sending over your file, In this specific example prior to opening the file in Designer, I opened it in illustrator and found that it consisted of two artboards, 'Artboard 61' which when edited in the Artboard panel was 13046x8800.96px: and a secondary artboard '01' which was 2205x1240. Since the .AI file is saved out with PDF compatibility these artboards are interpreted in the PDF data stream as pages, since we're opening the file in Designer, PDF pages are converted to artboards. When i've imported the .AI file into Designer at the default 72DPI and then checked the artboard dimensions after converting my document unit of measurement to pixels, these then match up with the dimensions shown in Illustrator: Page 1 = 'Artboard 61': Page 2 = '01': It's important that the .AI file is imported into Designer at 72DPI to maintain the same pixel values that were shown in Illustrator, if you leave the PDF import options on 'Estimate' it may import at a different DPI value skewing the pixel resolution, like in Hangman's example above.

Hi @rai44, Thanks for confirming that this isn't related to those two factors, just needed to rule out it being anything related to them initially. After repeating the test again and re-watching both recordings I'm seeing exactly what you have described, the cursor (Bluetooth mouse or magic keyboard) does not change to a text caret when actively hovering over text in a text frame. I had initially mis-interpreted this as it's not possible to insert your text caret using a mouse/trackpad input when it is, it just lacks the precision shown in other apps such as notes and can result in issues when trying to place the insertion point. Going back to V1 it doesn't look like the cursor has ever had this functionality within the apps, but I do think this still needs logging so I'll be logging this internally as an improvement. 🙂

Hi @rai44, - The Affinity apps have not been updated to officially support IOS 17 which can result in some unexpected issues whilst using the apps, since it's currently in a preview beta official support should hopefully be added nearer the time of the IOS updates official release. Compatibility may also be added at a later point during the current 2.2 app beta cycle. - In your screen recording you also appear to have stage manager enabled, this is also not officially supported currently which can result in certain issues, we don't have any news to share as to when stage manager support will be added currently. I'm not sure which of these or if either is even causing the problem in this specific scenario but i've not been able to re-produce an issue with placing the text caret using a bluetooth mouse. I would first suggest disabling Stage manager, restarting the app and then trying again. If not, it could be related to IOS 17 so it would be worth rolling back and then trying again.

Hi @Bryce, Instead of using the divide function to split the added curves apart which will delete any clipped/nested layers have you tried using Layer > Geometry > Separate curves? Your artwork should then be retained and nested into the curve at the bottom of the layer stack after separating them. You could then convert the now-separated individual curves to artboards (one at a time, I don't think this function works for multi-selections) via the Layer > Convert object to artboard and then re-position your artwork on the artboards accordingly. If you're still having issues, could you possibly upload a copy of your file/another sample file so we can see how your document is laid out prior to the divide/separation?

Hi @BBG3, When .AI files are opened in Designer only the PDF data stream is read, the proprietary .AI data is omitted, which is why .AI files need to be saved out of illustrator with PDF compatibility enabled. Because of this they are imported using Points unit of measurement which is the standard measurement for PDF files, you can freely change this after importing the file in Document Setup. After importing an .AI file containing two 730x730px artboards at 72DPI into Designer, both artboards have been imported in at 730x730pt/px as expected, could you perhaps provide the .AI file you referenced in your example which imported at 1070.7pt/px? Many thanks!

Ah that makes sense, no worries!

Hi @Hangman, This is a regression over 2.1.1 and is currently logged with the developers, i've now bumped it with your report. For future reference, since this is a 2.2 beta regression not in the release build, it's best to log these types of issues over in the beta forums bug section for the visibility of the QA team. 🙂

Hi @Al O welcome to the forums, From your screenshot it looks like you have toggled the visibility of the composite red channel via the channels panel, which is a purely visual preview of how your image appears without the red channel of your RGB image on the canvas only. If you wanted to permanently apply this look to your image, with the 'Background' layer selected in the channels panel you could right click 'Background Red' and then press 'Clear' to clear the red channel data on that particular layer. More info: https://affinity.help/photo2/English.lproj/pages/Channels/channelsSelectingEditing.html https://affinity.help/photo2/English.lproj/pages/Panels/channelsPanel.html

Hey @retrograde, I wouldn't be able to specifically comment on how difficult the feature would be to implement since i'm not part of the development team, however regardless of the feasibility if this is something you would like to see implemented feel free to make a post on the feedback section of the forums, personally I think it is a good idea. 🙂 https://forum.affinity.serif.com/index.php?/forum/122-feedback-for-the-affinity-v2-suite-of-products/

Hey all, Thanks for the additional findings along with the screen recording, I've replicated this issue on Windows and logged it with the developers. 🙂

Hi @anto, It looks like @Return raised some good points and examples as to how duplicating master page layers can be used in your original thread, and the ability to duplicate master page layers isn't a bug in itself. 🙂 This is a good suggestion, but again fits in better as a feature request to optionally prevent/restrict the renaming of master page layers rather than a bug with existing functionality.

Hi @bbrother, Many thanks for providing detail along with the recording, i've replicated both issues and it has now been logged with the developers.

Hi @yoyoboy welcome to the forums, Please see the FAQ I've linked below which details how to re-download the V1 apps via the 'Purchased apps' section of the App store.

Thanks for the additional detail and clarification, I'm seeing exactly what you mean after changing the 'Use Overprint Preview' setting in Acrobat to 'Always' and ignoring the Output Preview tool, only the Passthrough PDF/X files actually show an overprint preview on the canvas, while non PDF-X documents appear to have no overprint. In my original post I was too focused on the Object Inspector tool to assess this rather than the page content which interestingly does show that the three objects are set to overprint (Overprint= 'True'), it just fails to show this on the page content. If I just open one of non PDF-X documents directly in acrobat without placing it in another doc, the overprint preview shows correctly. I'll do some more digging and get back to you on this, as it does look like a bug. Okay, thank you, that would be really helpful, I'd be very interested to understand if that is the case and if it can be fixed. I've since confirmed with QA that this needs logging and have now logged it with the developers, particularly since it can maintain the Spot colours on Interpret. 🙂

Hi @Hangman, For my screenshots/examples I've used Acrobat Pro's Output Preview tool which is showing the overprint value as expected on non PDF/X placed files. I'm pretty sure the Output Preview tool is only available in the full version rather than the free version of Acrobat (if there is another way to check this, let me know). Which other PDF reader app(s) are you using to check the overprint preview for comparison? I'll raise this internally and come back to you on this one, as it currently looks like a object property which isn't interpreted.

Hi @Return, Good spot, I've logged this with the Docs team for the file path to be corrected in the help guide to the following: C:\ProgramData\Affinity\Common\2.0\Dictionaries Placing your dictionary files in the above directory will ensure that all three apps have access to the dictionary files, rather than the C:\Program Files directory which will only be accessible in Publisher.