StainX

We are pleased to announce an update for the Windows release of Affinity Publisher 2, version 2.0.3
We plan to also release this build as a MSI/EXE installer. Please follow this FAQ thread for notification of it's release.
The changes in Affinity Publisher 2 for Windows 2.0.3 (those made since the last release Affinity Publisher 2 for Windows 2.0.0) are as follows:
Fixes & Improvements:
New Document: Custom Document Preset order is not retained between app sessions afpackage fails to find Resources on Open Fixed spurious future version error under certain circumstances Improvements with PDF Import and Layers Fixes for RTF import - font name discrepancies, fields in footnotes Update for HEIF importer DWG Import scaling improvements Opening and closing chapters in a Book can leave the files locked / read only Crash opening a bunch of chapters from a Book simultaneously Colour Panel now remembers user preference for CMYK documents Export Panel UI fixes Preview exported PDF fails on Book exports Fix for export of Books with Bleed Fix for Booklet printing model Fixed some tool drawing issues relating to selections across spreads etc Pen tool tweaks and fixes Fixed hang that could occur composing vertical centre aligned text OpenType handling does not respect lookup flags such as IgnoreMarks Hit box of scaled text could be incorrect Gradients on text strokes don't render unless the fill also has a gradient Fixes for line breaking in some odd cases with punctuation Merge runs of tabs using leaders Resource Manager updates Fixed various issues involving handling of placed document files Placed documents with bleed can fail to render the bleed correctly Light UI Improvements Many and various Layers Panel updates and fixes Clipboard: 32 bit DIB support added Auto Flow Place: Added an option to auto-flow place to replace the content of already populated picture frames More attributes are retained when replacing images in frames Pages Panel, double clicking does not zoom page to view Ensure global colour edits update live Select Same Name should only select objects with user supplied names New clearer icons for stroke properties (cap, join, align) Hidden/Empty columns/rows are ignored when importing xlsx files into Data Merge, causes fields to get out of sync Help & localisation improvements. Licensing and Registration improvements and new help links  
UPDATING TO THIS VERSION (Free for existing customers)
The software version can be seen on the splash screen and the About dialog (in Help > About Affinity Publisher ).
If you’ve purchased from the Affinity Store — each time you start the Affinity Store software it will check for updates and offer any available update. The latest update will install over the top of any earlier version, with no need to uninstall. You can download the latest installer by logging into the affinity store here and find the order in your account and use the "Download" button in there. Alternatively, this new release (and previous versions of Affinity Publisher for Windows) can be downloaded from this link. (those installers are NOT for Windows Store purchases).
If you’ve purchased from the Microsoft Store — Microsoft Store updates are done automatically by the operating system (each time you start the application). If this does not happen for you, open the Windows Store app and click the three dots in the top right corner of the app and then go to Downloads and Updates. Click Get Updates. This should hopefully force the update to show.

I must say that this doesn't affect me so much but it is driving my sister crazy.
She has a lot of clients and is constantly jumping between them so this is a constant source of mistakes for her.
At this point this should be a priority, especially as this is the behavior from Adobe’s applications, this would greatly help newcomers 😇

Hi,
I think this has not been asked as of yet (at least, I can't find it when searching). Probably, most of us are interested in IDML import, since the most urgent thing is transitioning from ID to APublisher.
However, I think that the ability of exporting IDML is still very important in a professional context.
1) Most of the professional publishing sector will be based on ID for years, and being able to transfer our files to a larger workgroup is very important to have our work accepted.
2) Computer aided translation tools are usually compatible with IDML files (and I can confirm they can be perfectly compatibile with ID). Translating our work will probably mean that the translators will ask us an IDML file.
So, I hope to see this implemented in a near future version.
Paolo
 

I had my hopes when I saw the announcement the other day for v2, but we are dissapointed yet again. It was the first thing I checked once I purchased it. While it doesnt change my buying decision, I will just never understand why they cant give us the option to have the export settings linked to the file instead of the last settings that were used. Even Canva.com realizes this is an important feature and the give you a checkbox to save the export settings in the export workflow.  

Keep getting rained off laying a brick path in my garden so thought I’d make a few spirals in Inkscape and import them into Affinity Designer, these are linear spirals and start at 1 turn up to 40 turns in 5 turn increments after 5 turns.

Linear Spirals.afdesign

Please don't ask how and why this is possible - it works.

A Stand of Trees
Experiment with new Vector Tree Toolkit
All Vector 1500 x 600mm 300dpi
Created partly from New Tree Toolkit containing 6 vector tree assembled elements and textures as part of the Untamed Project
 
 
 

Wouldn't agree with this. Saving and exporting are two very different functions and it's appropriate and useful to keep them distinct, as in fact does Publisher's major competitor, InDesign (if you're comparing with other software).
Saving is related to the working .afpub file as a whole. (Ditto saving to a package.)

Exporting on the other hand is not "saving in a different format" so much as pushing out specific versions or portions of that file for particular use cases, e.g. 
• selected high-quality PDF pages/spreads for client proofreading and approvals 
• PDF edition for online publication
• PDF print-ready file for a printer
• JPEG/PNG/TIFF files of selected pages for use as images in different contexts, e.g. for a portfolio or presentation
• etc. 
When I export I'm assuming that the saved source/working file that I have open is not changed in any way.  

+1 from me 
The unconventional and unintuitive file-saving behaviour is a constant source of frustration and misplaced files. Especially when I'm working on multiple projects for different clients in the same day/week. I'm astonished we've all been putting up with this for years now. Publisher is so good in so many ways, it's a pity that a flaw like this causes unnecessary friction when, it seems to my non-developer eye, it would surely be easy to fix.
 

Hey there!
Anyone else have a very low scroll speed on the Pages Studio?
I mean, using the  Scrollwheel is a pain, at least if i set the Page Preview to small its working as intended.
(Using Windows 10, no special mouse software installed, 3 Lines per Scroll set in Windows 10)

Hi!
So i made some AHK script as Affinity Publisher always uses last used folder for export.
Would be a handy time saver to set the default output folder to the one the file you work with is in, right?
Here you go:
Just make sure to set or adjust the hotkey for "Open Folder in Explorer" in Files menu, i use Ctrl+Shift+E
I'm not super professional coder and AHK is sometimes behaving a bit inconsistent, so let me know how it's working on your system.
#NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases. #Warn ; Enable warnings to assist with detecting common errors. SendMode Input ; Recommended for new scripts due to its superior speed and reliability. SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory. #SingleInstance, force ;#NoTrayIcon ;if everything is working fine for you, you might enable that line. #F12::ExitApp ;Quit Script with Win+F12 #IfWinActive ahk_exe Publisher.exe !^+s:: { ;We are working in Publisher,so we get the window id: hwndPub := WinActive("ahk_exe Publisher.exe") ;Open Folder where the File lies!: BlockInput, On ;make sure nothing interrupts the hotkeys and to keep the right window active Send, ^+e ;You should set an hotkey for "Open Folder in Explorer" in Files menu, in that example its Ctrl+Shift+E WinWaitActive, ahk_class CabinetWClass,,2 ;wait for explorer to open up. BlockInput, Off if ErrorLevel { ;timeout occured! (Also happens if the file is not saved in the first place) Send, !^+s ;open export window non the less, but without the path magic return ;and exit } BlockInput, On Sleep, 100 ;tiny buffer just to make sure everyhing is ready. Path := GetActiveExplorerPath() ;get the path of the folder where the file is in. WinClose, A WinActivate, ahk_exe Publisher.exe Send, !^+s ;Affinity Publisher default hotkey for Export Alt+Ctrl+Shift+s BlockInput, Off WinWaitNotActive, ahk_id %hwndPub% ;Main Publisher not in Focus anymore! WinWaitNotActive, Export ;Wait for export window to close (this also includes the more options window) WinWaitActive, ahk_class #32770,,3 ;wait for save window with timeout! if ErrorLevel return ;timeout occured! ;now enter the path of the file source folder! BlockInput, On Sleep, 300 ;tiny buffer just to make sure everyhing is ready. Send, {AltDown}e{AltUp} ;windows hotkey to go directly to address bar, as writing directly to control seems messy on win11 Send, %Path%/{enter} ;send path BlockInput, Off } return GetActiveExplorerPath() { explorerHwnd := WinActive("ahk_class CabinetWClass") if (explorerHwnd) { for window in ComObjCreate("Shell.Application").Windows { if (window.hwnd==explorerHwnd) { return window.Document.Folder.Self.Path } } } }  

Originally Posted September 24, 2019 in the Feature Request Section - since then many people have posted to add their voice ! Someone suggested Posting it here also, so I have. Affinity is a Superb and Affordable program which I use all the time. I'm grateful that it exists and I recommend it to everyone.
Whenever I choose Save As or even more important File Export Save As, I end up in my Windows Default Save location (Drive and Folder), which I never want, so I end up wasting a lot of time browsing to the correct folder. Almost always this is the location from which the file was loaded. I looked but I was not able to find any way to set this in the Preferences.
It would be extremely useful to allow the user to be able to enable such a feature:  Save As and Export Save As to use the Source Folder of the File.
 
Thanks,
Dan

I would very much like to see this impemented.

Let's just keep this thread for what is is and was.
 
Simple basic feature that should be present since the very first alpha / beta version
Below here is just an example, dropdown list with multiple options would not be much more work.

To: Craigleeus
Nicely done, especially the idea of having the default be the prior setting. Perfect for those of us who want to save back to the Source folder 95 % of the time, but on occasion would like a different folder destination. Very nicely done.
If only Affinity would pay attention and implement it. They had an opportunity with the last update, but FAILED to implement it. What a shame, since this type of thing is not at all difficult. No AI needed, no Rocket Science.
Affinity used to really pay attention to feedback so I'm wondering what happened.

There I was with Affinity 1.10... Hoping...
From within my own little organised folder structures. I open a simple jpg in affinity...
..."save as" and "export" completely ignores the source path for that simple little jpg - as if it is completely unimportant.
If Affinity made a car, it would be a fantastic drive, efficient.... economic... 
....but you'd have to clamber in and out through the boot every time.
*Sigh*
 

Exactly as you say, but an icc color profile different from the color profile in use in the document, it always comes, in any case converted from a source profile to a destination profile, instead the exact procedure is that it must always keep the numeric values and never convert to destination (unless appropriate user requests).
In practice, with "no profile embedded" images it behaves well in this way.
Now that I remember well "the Adobe theory" there are 3 criteria of choice in color management in Adobe Suite.
1. deactivated
2. maintains the embedded profiles
3. converts into a work profile
the right choice is 2, it keeps the numerical values embedded in the color profile of the file. Put simply, consider that photo as if it had no color profile applied and read only the numerical values applied to it.
Then in the PDF / jpg export phase etc, you decide to "keep the numerical values" and apply a color profile of your choice, which can be either the work document or other.
Practically if I have a fogra39 profile document and I insert images with the fogra39 profile embedded, the numerical values are read in the right way. If I change color profile to the working document and I put fogra27 example and I click Assign, the color profile in fogra27 will change and the numerical values will remain the same as before (and it works well), but if I then have a fogra27 document and insert an image again with different profile eg fogra39, this image will be converted and numeric values will change.
In practice, when inserting a photo AD always applies a color conversion in the destination profile !!!! Even if the Convert colors box is not checked in the color preferences.
I don't think the color assignment command works well.
The color profile of the document should be ASSIGNED to each image inserted, imported, linked to the document so as not to VARY the numerical values even if you work with different embedded color profiles.
CAUTION!!!
Working appropriately with color management in the press, web, etc. (but above all in the press) is FUNDAMENTAL!
Incorrect conversion of numerical values can lead to serious financial damage during printing!
A trivial example if a 100% black is converted to a rich black 80-80-30-80 is not the same thing!
Not to mention color change in images or dominant etc ..
this thing is very delicate Attention Affinity !!!

 
It took me years of study to understand how the "good" thing works in Adobe, now here I find myself headed and above all with the awareness of a wrong management by the software.
Affinity we would love to leave Illustrator (because it's shit!) But you have to be able to do it without problems!
 

This is one reason why i keep saying any new document should open a new document palette and the colours should be added automatically to the palette when either created on the paste board or pasted onto pasteboard from elsewhere.

I noticed that a number of automatic adjustments such as auto levels and auto contrast are available as buttons in the menu, but there is not an "auto" button on the equivalent adjustment window. 
But moreover, the parameters of any auto adjustment, are not exposed, and not adjustable later on.
I would like to propose to implement either of both of the following:
add a button on the adjustment window (for all adjustments where it makes sense) to adjust the relevant parameters automatically (resulting in the values and slider positions to be adjusted accordingly). When any of the existing auto buttons is clicked, an adjustment layer is added (like when starting the equivalent adjustment), and the settings found by the software are shown. This will offer (in hopefully most cases) a good starting point to the allow the user to fine tune these settings.

Hey, James !!
Thanks a lot for the help!

They're not set by default, but you can assign them by going to Preferences>Keyboard Shortcuts. You should see them straight away if you're on Mac. If you're on Windows, scroll down slightly to see them.
Worth noting that you'll need to switch to another persona category at the top (e.g. Liquify) to set a shortcut for the main Persona (Photo, Draw, depending on the app). Hope that helps!

Hi, all. I've been browsing the forum for existing topics pertaining to Publisher's Resource Manager. This very necessary tool could use some development.
I'll definitely 'second' the request for this tool to be a docking panel ('studio'); it's conspicuous to have to manage linked/embedded resources in this separate tool, versus being able to do so on-the-fly during composition. I'd also move to have filters for link status, or some kind of indication of which ones have a problem. I just opened a document with missing links, but I had to hunt through the (collapsed) list for the missing items. N.B. I'm reluctant to have the software automatically update modified links, due to layout changes that might not be obvious.

@thomaso Thank you so much! That workaround saves ma lot of time!

Oh and there is still a bug with BoundingBox detection on some linked .afpub files, which messes up placement (my workaround is to use .pdf instead of .afpub).

That's why I mentioned above the grayed-out button as soon more than 1 image is selected. Feels like a weird bug.
Workaround: There are limited situations where replacement of a selection of more than 1  is allowed. Though it requires APub it might help you since you talk about a copied artboard and hundreds of replacements: If the images are placed in Picture Frames then the Replace button in the context bar may be used also for selectively selected items (but not the according button in Resource Manager for any odd reason). If it would work from the Resource Manager we could also replace selected sources of different pages. – I definitely wonder why Apub is coded to require additional objects (Picture Frames) to allow this kind of replacement of these object's contents (= frame's images).

replace images via picture frames.m4v

Last I saw of anything from Serif staff on this was that CMYK print would require too much work (I think the wording was something like "it doesn't come for free from the OS"). Exporting to PDF is still the only option.