Matthias

@Mark Oehlschlager the start/end nodes are the most likely of all to have issues due to the fact that a freehand pencil/brush tool has lots of noise at the start/end. I suspect @retrograde used a Pen tool to create the source curves?
Using your pencil/brush freehand approach, if you cleaned up the start/end nodes and then hit expand stroke, you'd probably find the results make a lot more sense. I'm just trying to say that the result of the Expand Stroke is correct, but the input given to it (from using the Wacom) is noisy, so you get noisy data out at the end, if that makes sense?
Yes, I do wonder if the 'tolerance' of the fit could be a user-adjustable parameter...  
Matt

Just a thought, but if the tolerance is a simple numeric input would there be a reason not to provide a slider in Preferences somewhere to control that?

Thanks, Matt!

Jey, Finally!
I was able to sucessfully add the used colours from an existing document to my document palette using "Add To Swatches From Fill". And the numbers stayed the same!
But if I select "Create Palette From Document" it's still converted colours (I suspect cmyk-to-rgb-to-cmyk) which makes wrong and tinted colours.
 
Also: "Add To Swatches... As Global" works kind of, but not really links the objects to the colours:

Bildschirmvideo 2020-01-10 designer1802.mov

Why is it that when one applies and adds a Pantone spot color to an object in one's document, that the swatch for the Pantone spot color in the Swatches panel is labeled generically "Global Color X" by default, rather than being labeled by the actual corresponding Pantone spot color number? (See attached screen grab.)
If we're wanting to manage inks, including spot inks, within our documents, swatch collections, and files sent to offset print services, shouldn't the Affinity software correctly label color Pantone color swatches by default as they are added to the document Swatches panel?
 

Here's the thing for me, if I select an already named spot color, it should use that name by default. If I so choose to rename it to identify its use, then so be it. But I rarely do. Why? Which name should I use if the same spot is used for headers, sidebar elements, and/or other elements? While that can be resolved, just using the spot name is, and has been, understandable for me.

Status: Beta
Purpose: Features, Improvements, Fixes
Requirements: Purchased Affinity Designer
Mac App Store: Not submitted
Download: Download
Auto-update: Not available.
 
Hello,
We are pleased to announce the immediate availability of the first beta of Affinity Designer 1.8 for macOS.
Affinity Designer 1.8 is a significant change to the currently shipping 1.7 version. Files edited in this version will not be backwards-compatible with the shipping 1.7 version. As such, we would not recommend using this 1.8 version for critical or production work at this stage. It is inevitable that there were will be a number of issues with 1.8 but we hope these will be minor and aim to resolve any issues very quickly, so please use it and explore the improvements, but also do keep in mind that you may find snags and we would appreciate your help with finding and reporting these to us.
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
With all that said, we hope that you will enjoy the new capabilities introduced in this release and we look forward to any and all feedback you give to us.
Many thanks!
Matt
 
Fixes
Overhauled the “File -> New” dialog - user templates are now supported Implemented unified toolbar for appropriately modern macOS versions Improved the results of Expand Stroke Improved the reliability of Boolean Geometry operations Fixed issues with grids which appeared to jump while zooming and had issues with gutters Improved dragging objects between artboards (takes into account "Edit All Layers" toggle) Improved geometric add to allow a single shape so we can unite shapes to remove overlapping areas Improved SVG export to not simplify structure, as some people require the original structure Fixed Styles to show styles that would normally be invisible Fixed selection of artboards and / or contents Fixed EPS import sporadically failing to load objects Fixed PDF export so embedding colour profile always converts image colour spaces to match the profile Fixed crash when loading some corrupt JPEGs (valid image data, but corrupt following data) Improved embedded document bounding boxes Fixed deletion of brushes / styles / etc to actually remove the raster data (to reduce file size) Fixed PSD export to include checks for empty rasterised layers Fixed PSD export of hidden layers Fixed angle cursors when the view has been rotated Fixed Layer Effects not handling changes to document DPI when the dialog is open (using Points as a unit would continue to use the old DPI) Fixed crash on vector export for specific arrangement of composites and clips Added Remove Columns button on the context toolbar for Designer and Photo for text frames with columns for documents created in Publisher Improved memory use with branching undo history and with replacing image nodes Updated PANTONE Solid and Bridge Palettes Fixed Create Palette from CMYK images results in RGB colours Improved performance of operations with large selections and improved performance of making selections of large numbers of objects Fixed selection problems with multiple objects of varying line weights Improved PDF import support for DeviceN bitmaps based on LAB colour space Improved PDF export of clashes between bitmaps with/without k-only Fixed PDF export "Rasterise nothing" allowing through bitmaps with alpha channels Fixed crash importing PSD files containing embedded colour profiles with unicode characters in their name Improved performance of PDF import with groups containing more than 5,000 children Fixed OpenType that could fail to apply 'liga' near end of line Fixed Text Justification to split ligatures correctly Improved PDF import matching of unknown fonts  
To be notified about all future Mac beta updates, please follow this beta notification thread 
To be notified when this update comes out of beta and is fully released to all Affinity Designer customers, please follow this release notification thread

If you want it to auto update you can enable "Automatically update linked resources when modified externally" in Preferences > General - If you don't enable this we will used the image as it was inserted, but the Resource Manager will show it as modified indicating the source no longer matches what we have in the document

Actually, it gets stranger than that.  I just did this in Designer since I happened to have it open, but I suspect Publisher would be the same?
 
I had a simple rectangle with a global color assigned to it.  I copied it and pasted it into a new document that has a different color profile assigned.
In the new document, if I select that rectangle, the Color panel shows the "Global Color 1" assigned to the rectangle - but there is no document palette in the document, and thus no global colors.
Somehow the rectangle is keeping the assignment of the global color across the copy, even though the global color doesn't exist in the target document.
 
 
Based on that, I am forced to agree that there is definitely a bug here somewhere.  As to the global color itself not being copied over to the new document, I would consider that a missing feature.  However, if the object remains assigned to a color that does not exist in the new document, that is definitely a bug.

See, that's where I think some misconceptions shows: The App has to differentiate between objects with colour profiles attached and swatch-opjects (usually cmyk) which are not colour managed aka "source"-values.
A source must never be changed. You should only attach some colour profile, which maybe changes colours at PDF output. 
While designing and copy pasting this should not convert by default, although you may have the option. 
When exporting you would have the option, like in InDesign, to temporarily "convert colours" or pass the values thru (preserve numbers) -> which only applies to swatch colours, not RGB-Images.
   
The ID Info Text reads:
"Colors will be converted to the destination profile space only if they have embedded profiles that differ from the destination profile (or if they are RGB colors and the destination profile is CMYK, or vice versa). Color objects without embedded profiles and native objects (such as line art or type) are not converted, so that the color numbers are preserved."
 

I agree with every you say, and especially this. The conversion is happening without my knowledge - baffling to me that anyone would want this.

True.
But I think as long as it is a colour that I have defined as a global colour it should always stay the same, regardless of the document’s colour profile. I’d also expect the according swatch to show up in the new document (which it doesn't).
I’d prefer my global colour looking weird in a different colour space. Numerically (but kind of secretly) changing the actual colour values is a recipe for disaster when you have to work with people that are not so much into colour management (I’d guess it is the majority). Because once the app has benevolently changed ”my“ colour’s numerical values in order to keep it’s appearance a third party cannot ever trace it back to it’s original values (which might have been there for a reason). Whereas it’s easy to change the document’s colour profile anytime to match the intended output (or the global colour itself, provided the swatch is being copied over, too).
Since numerical colour definitions (not colour appearances) are a customary thing in corporate design I am actually baffled that this is a topic that’s being discussed at all.

True.
But I think as long as it is a colour that I have defined as a global colour it should always stay the same, regardless of the document’s colour profile. I’d also expect the according swatch to show up in the new document (which it doesn't).
I’d prefer my global colour looking weird in a different colour space. Numerically (but kind of secretly) changing the actual colour values is a recipe for disaster when you have to work with people that are not so much into colour management (I’d guess it is the majority). Because once the app has benevolently changed ”my“ colour’s numerical values in order to keep it’s appearance a third party cannot ever trace it back to it’s original values (which might have been there for a reason). Whereas it’s easy to change the document’s colour profile anytime to match the intended output (or the global colour itself, provided the swatch is being copied over, too).
Since numerical colour definitions (not colour appearances) are a customary thing in corporate design I am actually baffled that this is a topic that’s being discussed at all.

I think the discussion about how we don’t need user-defined compositions of colour since the printing process itself is flawed (and paper variations making it even worse) is beside the point.
Yes, there are many variables that can render a colour different than intended. But that doesn't mean relying on one’s own colour definitions is superfluous. It is a necessity for reasons like rastering or tinting or overprinting or for simply passing them on.

Once an element is attributed with a defined global colour this colour swatch (including it’s colour space and according values) should be tagged to the element, regardless where you copy it. In corporate design work this is a must. Consider how this is handled in InDesign: When I need a certain defined colour in a new document I just copy an element containing this colour from a previously made document into my new document — and then maybe even erase this element. But the attached colour swatch is being copied along with the element and — Bingo! — there it is in my colour palette, ready and willing to be utilized.
This makes sense even if you copy a cmyk swatch over to an rgb document for, say, web design. As it is a global colour you can simply change the swatch (and thus any element using it) to match your predefined corporate design colour in rgb colour space should you want to have control over the conversion (otherwise the app does it on the fly).
A designer ultimately has to be in charge of numerically defined colour values — regardless whether the app ”thinks“ it knows better. The very idea of a global colour swatch is an expression of this paradigm. Otherwise she can always use the colour picker or mix something in the colour wheel. Defined values often have to be communicated to third parties to ensure everyone in the design process is on the same page.  With the Affinity Suite — as much as I truely love it — the handling of colour swatches is confusing and should be overhauled.
To reiterate: Once I, the designer, have defined a global colour “with my own hands” it’s colour values should be an attachable and thus copyable asset and must be sancrosanct in any document.

Once an element is attributed with a defined global colour this colour swatch (including it’s colour space and according values) should be tagged to the element, regardless where you copy it. In corporate design work this is a must. Consider how this is handled in InDesign: When I need a certain defined colour in a new document I just copy an element containing this colour from a previously made document into my new document — and then maybe even erase this element. But the attached colour swatch is being copied along with the element and — Bingo! — there it is in my colour palette, ready and willing to be utilized.
This makes sense even if you copy a cmyk swatch over to an rgb document for, say, web design. As it is a global colour you can simply change the swatch (and thus any element using it) to match your predefined corporate design colour in rgb colour space should you want to have control over the conversion (otherwise the app does it on the fly).
A designer ultimately has to be in charge of numerically defined colour values — regardless whether the app ”thinks“ it knows better. The very idea of a global colour swatch is an expression of this paradigm. Otherwise she can always use the colour picker or mix something in the colour wheel. Defined values often have to be communicated to third parties to ensure everyone in the design process is on the same page.  With the Affinity Suite — as much as I truely love it — the handling of colour swatches is confusing and should be overhauled.
To reiterate: Once I, the designer, have defined a global colour “with my own hands” it’s colour values should be an attachable and thus copyable asset and must be sancrosanct in any document.

You're right: I checked, one was "iso coated v2" and the other was "iso coated v2 300%" –> I made a new document with the same profile and now the copy operation does no color conversion anymore.
You're NOT right: When I define my corporate design colours, the NUMBERS ALWAYS have to be the same. When exporting as PDF, there will be a color profile added, or an output intent, but in a correct colour management workflow, that should not matter in the layout process. 
Only for placed images, this is an option – as most of the pictures are RGB anyways.
I don't want the box to be subjectively "black" – I want it to be exactly 0c0m0y100k-black, no matter what.
 
So as I said: this is a bug.
And as I now tested in the 1.7.3 release:
the conversion bug is the same (with different profiles) the global colour is correctly transferred to the target document ...although it does not import it to the document palette, nor does it make a new one. The colour system inside affinity apps obviously still thinks it deals with images and does not fully embrace the concept of precisely predefined "swatches" 

Status: Beta
Purpose: Stability and General Testing
Requirements: Purchased Affinity Publisher
Mac App Store: Not submitted
Download: Download
Auto-update: Not Available
---
Hi,
We were surprised and delighted that Publisher was awarded Apple's macOS App of the Year last week, and of course, this is where it really all happens, so we would like to thank you once again for all of your feedback and input. We would not have made it so far and so fast without you.
That said, it's pretty much business as usual, and we are pleased to announce that a new Customer Beta of Affinity Publisher (1.8.0.523) is now available as a download from the link above. Barring catastrophe this will probably be our last update this year.
As this is a 'Stability and General Testing' beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity where you may be adversely affected by the application failing, including the total loss of any documents. 
We hope you enjoy the beta, and as always, if you've got any problems installing or running up, please don't hesitate to post in this thread. 
Any problems actually using this version please make a new topic in this forum and we'll get back to you as soon as we can. Please feel free to leave general suggestions and comments in the Discussion Forum. 
Once again, many thanks for your continued feedback, and best wishes for the Holiday Season and the New Year.
---
StudioLink
This build of Affinity Publisher, 1.8.0 Beta, requires 1.8.0 Beta builds of Photo and Designer for StudioLink to function. We hope to make these available soon.
---
New Features and Major Improvements
Preflight
We have introduced a preflight check feature which can be used to ensure that your document exports or prints as intended. The preflight check runs as a background process, and can be run on on demand, prior to output, or 'live' on a continual basis. We currently have a number of separate tests with more planned for inclusion in the final 1.8 and in the future.
Preflight is configured via the 'Preflight' panel, which supports profiles to specify which tests should be run if you desire. An indicator is provided on the status bar for immediate feedback on the process. Note we have requested updated icons as we are aware that colour alone is not a good way to represent the different statuses.
Please feel free to suggest additional tests - it's likely that many will already be under consideration but please don't let that deter you.
Fixes and Smaller Updates
New Document Panel
Panel is now resizable and modeless.
Reworked categories and subcategories.
Added multiple user template folder support.
Added Page Preset label (allow for `Custom`).
For those items with no previews, we draw the Affinity icon for now.
Excluded IDML files from quicklook preview.
Document Setup
Adding a page via menu / shortcut wasn't propagating desired properties.
(Win) Changing DPI in a facing page document could incorrectly cause pages to be resized.
General
(Win) Stock Panel search criteria is no longer cleared when switching providers.
(Win) Global Colour Picker was not using document's colour space.
Text
Space between paragraphs of the same style can now be set explicitly.
Stylistic Sets and Character Variants now show names in UI if defined by the font.
OpenType UI now uses feature descriptions from font and smarter samples.
Improved SmallCaps and CapsToSmallCaps handling.
Updated handling of 'Kerning' in Text Styles.
Fixed a couple of issues with 'Towards Spine / Away from Spine' UI.
Inline Text Frames were showing spelling errors in overflow.
(Mac) Fixed insets controls in Text Frame panel.
Fixed crash pinning to master page.
Fixed failure to report missing fonts for non character glyphs.
Drop caps 'Auto' now deals with inline images correctly.
Text in Text frames at very edge of page could show the wrong page number.
(Mac) Fixed insets controls in Text Frame panel.
(Win) Character Panel was not always reflecting current font properly.
Hyperlinks
Add ability to see and sort by hyperlink type. 
(Mac) Fixed crash when switching a file based hyperlink to use a different file.
(Mac) Fixed possible crash on showing Insert Hyperlink Dialog.
File Import
Some Embedded Documents could initially render incorrectly after re-opening host document.
Adding Pages from File manages mismatch in document transparency properly.
Fixed missing elements when importing specific EPS features.
Fixed crash on Windows when jpeg error handler triggered.
IDML
Fixed crashes on import for specific sample files.
Supports space between paragraphs of same style.
Improved import of unencoded glyphs.
XLSX
Fix for hidden columns.
Some text field types not imported.
Export
PDF/X-3 Embedding a colour profile was always converting image colour spaces to match the profile.
---
To be notified about all future Mac beta updates, please follow this beta notification thread 
To be notified when this update comes out of beta and is fully released to all Affinity Publisher customers, please follow this release notification thread

Status: Beta
Purpose: Stability and General Testing
Requirements: Purchased Affinity Publisher
Mac App Store: Not submitted
Download: Download
Auto-update: Not Available
---
Hi,
We are pleased to announce that a new Customer Beta of Affinity Publisher (1.8.0.499) is now available as a download from the link above.
As this is a 'Stability and General Testing' beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity where you may be adversely affected by the application failing, including the total loss of any documents. 
We hope you enjoy the beta, and as always, if you've got any problems installing or running up, please don't hesitate to post in this thread. 
Any problems actually using this version please make a new topic in this forum and we'll get back to you as soon as we can. Please feel free to leave general suggestions and comments in the Discussion Forum. 
Many thanks for your continued feedback.
---
StudioLink
This build of Affinity Publisher, 1.8.0 Beta, requires 1.8.0 Beta builds of Photo and Designer for StudioLink to function. We hope to make these available soon.
---
New Features and Major Improvements
Unified Applications Toolbars
Updated layout of toolbars in main application Window. (Mojave or later)
Text Editing Keys
Choose between 'Serif Defaults' or 'Apple Defaults' for text editing keys. e.g. Serif default for 'Move to Beginning of Word' is <Cmd>-<Left Arrow> whereas Apple default is <Alt>-<Left Arrow>. Available via Preferences.
Improved master page handling when adding single pages in a facing page document
Adding single pages to a facing page document with facing masters no longer shuffles master pages from left to right or vice versa.
Migrate frame contents when replacing Masters
Option to 'Clear' or 'Migrate' content when replacing a master which has modified text / image content on the target page. Available via Pages Panel 'Apply Master…' etc.
Re-order Master Spreads
Added the facility to re-order Master Spreads using drag drop in the Pages panel.
Merge Documents
Facility to merge specified pages from one document into the current document. Available via Pages Panel context menu or Document > Add Pages from File...
Linked 'Embedded Document' Resources
Better handling of Linked 'Embedded Document' resources to prevent files with such resources bloating on save.
Collect Resources
Facility to collect all up-to-date linked document resources in a single specified folder. Available via Resource Manager.
Find and Replace MRUs
MRU lists for recent Find and Replaces, available on the field drop menus on the Find and Replace Panel.
Anchor Panel
To manage Hyperlink Anchors. Access via View > Studio > Anchors.
PANTONE
Updated PANTONE Solid and Bridge Palettes for September 2019 update (Link)
Text Features
Last line outdent.
Drop Caps now let you set the number of characters dropped.
Indent to Here.
Add Right Indent Tab.
Insert from the Text Menu 
Added additional fields, plus option to show the Fields Panel.
TOC
Added option to skip line breaks in a TOC.
Added option to skip or include inline images in a TOC.
General Fixes and Minor Improvements
Open / Import
"Make a copy" and "Continue" buttons when opening a non-beta project file were reversed
Improve support for DeviceN bitmaps based on LAB colour space on PDF import
Document Management
When moving pages, transform pasteboard content so it doesn't end up on spread
Margins change with document DPI on non-master pages
General / Tools
Added option to make bleed of embedded Affinity documents visible
Strokes on master page objects now extend into the page bleed area
Setting K-Only for a missing linked image caused crash
Linked images that fail to load now fall back to previews
Fixed Populate Picture Frames across multiple artboards
Convert to Picture Frame was disabled for EPS
(Win) Create Palette from CMYK images imports as RGB
(Win) Fix for inconsistent document tabbing
Text
Can now use <Ctrl> / <Cmd> (Win / Mac) to link multiple text frames
When linking text frames stories are now concatenated
Preserve Manual Position not reflected correctly in Pinning Panel
Add special hyphenation rules for solidus (U+002F) to distinguish e.g. fractions
Changing spread / artboard in an Embedded Document now updates Text Wrap
Fixed default wrapping around Embedded Documents with transparency
Prevent table cell separators from being copied to non-tables (fix for non-deletable breaks)
Fixed auto-correct bug entering double spaces
Fixed line endings for Paragraph decorations
Now possible to remove arrowheads if inadvertently applied to Text Frame
Leading override could not be set to Auto in Text Style
Text with 'No break' did not always break before the no break
Fixed hyphenation issues in last line of column
(Mac) Missing font dropdown doesn't list missing fonts
(Win) Spell check identifies numbers mixed with other characters as incorrectly spelt
Tables
Adjusting Table properties for multiple cells fails if selected cell already has the desired property
Fixed possible crash when auto fitting table to text
Find and Replace
Fixes for skipping occurrences when replacing
Tidied up finding around end of text
Hyperlinks
Fixes for hyperlinks in Tables
Hyperlinks are no longer generated in PDF output if hidden
Fixes for Hyperlink panel not always displaying correct page of link target
Fixed hyperlink bugs when switching to / from facing pages
Glyph Browser
Glyph Browser now always renders glyphs at screen scale
DocX
Importing tables from docx files could fail to import formatting resulting in crash
Fields
Added yyyy-MM-dd date format
Resources
Linked images - Context toolbar not updated after converting to embedding
Filenames with underscores not displayed correctly in Resource Manager
Font Manager
Font Manager 'Locate' did not locate full runs
Export / Print
Prevent spurious warnings about overflow text in text frames that won't be output anyhow
Overprint Black now only sets to overprint if tint set to 100%
Fix for "Rasterise nothing" was causing PDF export failure in certain circumstances
(Win) Print dialog wasn't always removing the red overlay after page had been scaled to fit
---
To be notified about all future Mac beta updates, please follow this notification thread 
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread

A knife tool for splitting paths would come in handy.
Cutting open paths is optionless. When cutting closed shapes in two parts (or more, depending on the form) there could be an user definable option whether the resulting paths will be open or closed.
 
Matthias

This beta has been superseded by the release of Affinity Publisher for macOS 1.7.2 to the public. Check back on this forum for future betas
Status: Beta
Purpose: Improvements, Fixes
Requirements: Purchased Affinity Publisher
Mac App Store: Not submitted
Download: Download  (Download link removed as 1.7.2 is now live)
Auto-update: Not available
---
Hi,
We are pleased to announce that an updated customer beta of Affinity Publisher (1.7.2.458) is now available as a download from the link above.
If this is your first time using a customer beta of an Affinity app please note that the beta will install as a separate app alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
The beta is an incremental update to the 1.7.1 store version. We recommend that you use this beta in preference to your store version if you are affected by any of the issues listed below.
If you have any problems using this version please make a new topic in this forum and we'll get back to you as soon as we can. Please feel free to leave general suggestions and comments in the Discussion Forum.
---
StudioLink
StudioLink has been updated to improve reliability. However StudioLink in this Beta still requires the latest Beta versions of Designer and Photo to function.
---
Fixes and Improvements
Text
Fixed crash breaking path text curve for open curves
Fixed error copy / pasting Text Styles that could cause crash
Overlapping text frames now respect Ignore text wrap when wrapping around each other
Fix for Optical Alignment ignoring Tabs
Text selection highlight no longer includes generated list text
Fixed bug that could fail to apply OpenType features near end of line
Changing letter spacing now splits ligatures correctly
Fix for issue unpinning pinned nodes in pinned nodes
Fixed Pinned Node status not updating correctly when changed on Master Page
Fixed positioning issues when unpinning nodes
Hyphenation fixes
(Mac) Fixed further IME issues
Import / Export
PDF Import: Improved Font Substitution suggestions when opening PDFs etc
PDF and Vector Export: Fixed issue with Embedded Documents and Adjustments
PDF Export: Fixed Bleed not being saved in export profiles
PDF Export: Fix for unwanted clipping when text nodes exported 'as selection'
PDF Export: Fixed export of non-breaking hyphens
PDF Export: Avoid font preflight warnings when embedding TrueType CIDFonts
PDF Export: Web preset now embeds all fonts. Many browsers don't support ligatures unless the font is embedded and so render incorrectly.
(Win) Fixed occasional crash when printing
---
Earlier Release Notes Beta 442
To be notified about all future macOS beta updates, please follow this notification thread
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread

This beta has been superseded by the release of Affinity Designer for macOS 1.7.2 to the public. Check back on this forum for future betas.
Status: Release candidate
Purpose: Features, Improvements, Fixes
Requirements: Purchased Affinity Designer
Mac App Store: Not Submitted
Download: Download link removed as 1.7.2 is now live
 
Hello,
We are pleased to announce the immediate availability of the first release candidate build of Affinity Designer 1.7.2 for macOS.
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
This beta is an incremental update to the 1.7.1 version recently released to all customers. We recommend that you use this beta in preference to the store version if you are affected by any of the issues listed below.
Matt
 
Changes Since 1.7.1
- Improved usability with Apple’s Sidecar for macOS Catalina and iPadOS 13. (This build is still not notarized, so requires user action to allow it to run)
- Grid gutters reinstated.
- ‘Edit all layers’ can now be used to allow/disable artboard object reparenting during translation drag/object creation.
- Fix for bleed export options.
- Fix for issues with constraints on children of constrained objects which are used as clips.
- Fix for failure to load SVG colour 'none' causing import to stop.
- Fix for pen tablet barrel rotation input turning the wrong way.
- General performance improvements.
- Text performance improvements.
- Added ‘d’ default keystroke to restore objects to black and white colours.
- PDF export improvements.
- Added TGA export.
- Different icon for beta builds.
- Added a warning when deleting a global colour.
- Fixed broken Japanese keyboard input (sorry!).
- Fixed printing CMYK documents on older versions of macOS.
- Fixed crash when reentering export dialog under certain conditions.
- Fixed crashes when pasting screenshots into the app.
- Fixed loss of legacy HSL adjustment HSV state after a save.
- Assorted small fixes and improvements.
- Help improvements.
- Localisation improvements.
- Import 16bit half float JPEG-XR files properly.
- Improved LAB colour conversions.
- Pantone palettes are now sorted alphabetically.
- Fixed crash when starting app in a folder containing weird characters.

Status: Beta
Purpose: Improvements, Fixes
Requirements: Purchased Affinity Publisher
Mac App Store: Not submitted
Download: Download
Auto-update: Not Applicable
---
Hi,
We are pleased to announce that the first customer beta of Affinity Publisher (1.7.2.420) is now available as a download from the link above. Build 420 has replaced Build 419 which has been withdrawn.
If this is your first time using a customer beta of an Affinity app please note that the beta will install as a separate app alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
The beta is an incremental update to the 1.7.1 store version. We recommend that you use this beta in preference to your store version if you are affected by any of the issues listed below.
If you have any problems using this version please make a new topic in this forum and we'll get back to you as soon as we can. Please feel free to leave general suggestions and comments in the Discussion Forum.
---
StudioLink
StudioLink in this Beta requires Beta versions of Designer and Photo to function. We are hoping a Designer Beta will become available for macOS soon.
---
Fixes and Improvements
Import / Export
DocX import using File > Place was ignoring styles if no frame previously selected Other DocX import fixes for specific files PDF Import fixes for specific files PDF Export - Date format in Info now locale dependent Bleed control moved to 'More' options or removed for export formats where it is less relevant (Win) WMF import fix for specific file Resources
Linked resources were always updating when a document was re-opened Fix for 'Locate missing resources' on file open failing Replace image was always creating a linked resource Resource Manager was showing incorrect image size for some stock images Text
Fixed copy / paste from MSWord not always selecting RTF format Fixed issues with drag / drop and Master Page text Fixes for pinning / unpinning objects within Master Page text Fixes for Pinned objects and Path Text Text wrapping performance improvements Text wrapping around other Text Frames now honours z-order Text wrapping fixed for thin lines Apostrophes causing spelling errors / auto-correct issues Fixed issue preserving fields, index marks etc when correcting spelling Text Style Editor fixes Fix for some fonts not showing underline / strikeout List of used font families for current document does not refresh automatically (Win) Text Styles Panel - hyphenation setting is not reflected correctly (Win) Font handling improvements, new fonts not recognised if many fonts installed, instability when installing a missing font Printing
Fix for Empty Picture Frames being erroneously output to Print (Mac) Typing '0' in Pages under Range and Scale in Print dialog causes crash (Mac) Tiled and N-Up options in Print dialog can't be directly edited (Mac) Fix printing CMYK documents on older macOS StudioLink / Interop
Implemented 'Edit in Publisher' for Designer and Photo (Win) Photo - Creating a mask from selection now accounts for bleed settings Misc
Find and Replace with Paragraph style was only applying style to found text rather than whole paragraph Fix for ArtText not showing as selected if no fill is applied (Mac) Page outlines not always visible with white pasteboard (Mac) Fixed crash starting app from folders containing '/' (Win) Pantone categories are now alphabetically sorted. (Win) Asset names are no longer cut off in list view (Win) Object styles are no longer missing labels when using Grid View Help updates Translation updates To be notified about all future macOS beta updates, please follow this notification thread
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread

Do you not have a page chooser in the status bar at the bottom left? 

Hi Matthias,

As Walt has indicated these are not intended to be there. It is with development to be removed. With that said however file linking and embedding should make their way to Designer eventually.