Matthias

Yes please

Dirty? – I know that term as opposite of clean or failure-free. – At least concerning pixel waste, in times of climate , it appears more dirty to export/import a palette first. And even after doing so, a copied object would not have the imported swatch assigned.
 
So what? – Then this could get a solution, too. (as @Matthias described already)

Scenario 1: It could simply be named “cool color 2“, even if it’s identical.
Scenario 2: The user gets prompted what to do with those two competing swatches – a) replace the old one or b) keep both. Just like the macOS Finder works with two identically named files.
If you go with scenario 1 or 2b and now have swatches 1 and 2, you could still decide at any time to delete one of the two swatches, in which case Publisher/Designer/Photo would ask you with which swatch (or none) you want it to be replaced.

Maybe Global color... should be renamed Document color... as it can't be applied to an application palette.
And why name a newly created color "Global color 1", " Global color 2"... It's meaningless. Why not name it with its name (like Pantone 7557 C or by values). I have no way to see if it's a spot color CMYK, RGB...

(I am not using Affinity Designer nor Affinity Photo. Therefore I am not familiar with the  swatch window who is the same across the 3 apps.)

If I copy an object with a document-swatch assigned and paste it into another .afpub, then its swatch is missing.
This behavior is especially annoying because I seem to be forced to use document palettes – and must not use application palette only – if I want to use global swatches. So ...
–> A global color swatch is, in my mind, hierarchical over a non-global swatch.
––>  Since global swatches have to be in document palettes then, consequently, a document palette would hierarchical be over other palettes.
–––>  That makes it confusing, too: Whereas any application swatch is available in other documents, No swatch from a documents palette comes to another document with copied objects.
There seems to be no way to transfer selected object's swatches between .afpubs.

I'd personally like to see a tick box or something in preferences that would enable global colours by default, so even imported artwork would import as global - so many times I've imported a logo originally done in illustrator using a different colour profile and all the colours would be in a mess especially if the print provider needs all rich blacks to be no more than 260% density and the imported blacks are 380%, I've also had similar problems with artwork setup as a single 100% black importing CMYK at around 300% - just importing in the used colours as a global palate would save potentially hours of going through layers and nested layers to convert colours to global manually, this feature is a massive time saver with indesign - I'd also love to see preference tick boxes for scale fx and strokes to be on by default 
Heres a quick screen rec detailing how easy indesign does it, although theres a slight profile mismatch so the rich black loses it's values once pasted back into designer but would take an age to sort out in designer 
Globalz.mov

If the software kept track of whether or not the user had renamed the color then the name could easily be one that was selected to match the color up until then, but you would still wind up with people renaming them to things like "19-4150 - sidebar text" after which they would get out of sync.  Obviously that would still be possible with what I am suggesting, but there would be less reason for the redundant inclusion of the color in the name, so if people still did things like that they could only blame themselves for the confusion.

1. It would be Good to both have the color reference of the color (RGB, CMYK, ....) Both When you see only the small square with the color the possibility of a Tooltip when you pass over the color with the color percentages indicated
When entering the Pantone be renamed with the name of the pantone.
2. It would be good to be able to insert a color created in the color palette with a Drag and drop and insert it / add it in the palette.
3. I see the color palette management palette a little too cumbersome

Speaking of the Color Palette:
I would prefer if the predefined colors I chose kept their names in the document colors list. If I’d want to I still could rename them anytime. But a label like „Global Color 1“ doesn’t help. If it is e. g. PANTONE I sure would like to (and have to) know.

Bildschirmaufnahme 2019-05-23 um 10.13.30.mov

As much as I love Designer/Photo/Publisher I think there are a few minor UI issues where user actions don’t meet expectations. I already mentioned some of them, for example:
– Why not reveal the file path by alt-clicking on the document  title (standard macOS behavior)?
– Why not recognize the state of the alt key once dragging has started (standard Finder behavior)?
 
But my suggestion today is: I think the color handling in the color palette (or Studio) can improve with small refinements like:
– Add a command to delete all unused colors in the document/user color lists.
– Add a command to change all used colors to global.
– Make multiple color swatches selectable (and changeable, e.g. to global or for deleting) with alt-click (standard macOS behavior).
 
Cheers
Matthias

Furthermore, I'd appreciate for Resource Manager if ...
– a resource's file path would not get cropped for long paths but shown with line break instead.
– the Resources Manager would enable me to reveal a resource on disk. (f.i. double-click on file path or reveal button)
– using "Replace": the file path would appear on the the following OS window:
(which became placed over the Resource Manager window and covers the path there). (Works in various applications in macOS).
– on page selected resources which are used more than once would auto-open their folder in Resource Manager
(instead always highlighting the 1st item in the list)
 

Great, thanks Mark. Check it out right now.
Update: My v.330 files with linked resources operate just fine. Relieved.

As much as I love Designer/Photo/Publisher I think there are a few minor UI issues where user actions don’t meet expectations. I already mentioned some of them, for example:
– Why not reveal the file path by alt-clicking on the document  title (standard macOS behavior)?
– Why not recognize the state of the alt key once dragging has started (standard Finder behavior)?
 
But my suggestion today is: I think the color handling in the color palette (or Studio) can improve with small refinements like:
– Add a command to delete all unused colors in the document/user color lists.
– Add a command to change all used colors to global.
– Make multiple color swatches selectable (and changeable, e.g. to global or for deleting) with alt-click (standard macOS behavior).
 
Cheers
Matthias

Great, thanks Mark. Check it out right now.
Update: My v.330 files with linked resources operate just fine. Relieved.

I know it’s asking a lot. But now that linking seemingly works as it should it would be great if the Resource Manager (and/or the „Save As“ command) had a collection-building function where Publisher would copy every resource to a specified folder. Good for sharing work with colleagues and organizing jobs once they are done.
One great thing (like resource linking) leads to another …

As much as I love Designer/Photo/Publisher I think there are a few minor UI issues where user actions don’t meet expectations. I already mentioned some of them, for example:
– Why not reveal the file path by alt-clicking on the document  title (standard macOS behavior)?
– Why not recognize the state of the alt key once dragging has started (standard Finder behavior)?
 
But my suggestion today is: I think the color handling in the color palette (or Studio) can improve with small refinements like:
– Add a command to delete all unused colors in the document/user color lists.
– Add a command to change all used colors to global.
– Make multiple color swatches selectable (and changeable, e.g. to global or for deleting) with alt-click (standard macOS behavior).
 
Cheers
Matthias

I know it’s asking a lot. But now that linking seemingly works as it should it would be great if the Resource Manager (and/or the „Save As“ command) had a collection-building function where Publisher would copy every resource to a specified folder. Good for sharing work with colleagues and organizing jobs once they are done.
One great thing (like resource linking) leads to another …

Now that Publisher has image linking as it is supposed to be I guess we won’t have to wait for too long to see this feature in Designer as well. To counter the possible argument about how that is of any importance for an app that deals primarily with vectors: here comes a screenshot …

I have a pre-1.7.0.330 Publisher file containing a linked, multilayered PSD file. In the Resource Manager the resource shows up as “image_1.tif“ instead of the original PSD file with a non-generic name. Seems like Publisher exchanged the multilayer PSD file with an embedded, flattened one.
Now, when I replace this embedded .tif-file with the original PSD, save and close, the Publisher document becomes corrupted and can’t be opened anymore.
Update: Same result when I replace the embedded resource with a PSD file manually with ”Replace Document“ in the context toolbar.
Update 2: Seems to be logged already. Apologies.
Update 3: When I place the multilayered PSD separately, delete the embedded one and then save, the document is just fine and can be reopened after closing.

I have a pre-1.7.0.330 Publisher file containing a linked, multilayered PSD file. In the Resource Manager the resource shows up as “image_1.tif“ instead of the original PSD file with a non-generic name. Seems like Publisher exchanged the multilayer PSD file with an embedded, flattened one.
Now, when I replace this embedded .tif-file with the original PSD, save and close, the Publisher document becomes corrupted and can’t be opened anymore.
Update: Same result when I replace the embedded resource with a PSD file manually with ”Replace Document“ in the context toolbar.
Update 2: Seems to be logged already. Apologies.
Update 3: When I place the multilayered PSD separately, delete the embedded one and then save, the document is just fine and can be reopened after closing.

Now that Publisher has image linking as it is supposed to be I guess we won’t have to wait for too long to see this feature in Designer as well. To counter the possible argument about how that is of any importance for an app that deals primarily with vectors: here comes a screenshot …

Status: Beta
Purpose: Features, Improvements, Fixes
Requirements: Purchased Affinity Designer
Mac App Store: Not submitted
Download: Here
 
Hello,
We are pleased to announce the immediate availability of the beta of Affinity Designer 1.7 for macOS.
Designer 1.7 is a significant change to the currently shipping 1.6 version. Files edited in this version will not be backwards-compatible with the shipping 1.6 version. As such, we would not recommend using this 1.7 version for critical or production work at this stage. It is inevitable that there were will be a number of issues with 1.7 but we hope these will be minor and aim to resolve any issues very quickly, so please use it and explore the new features, 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.
It’s also worth noting that we aren’t done yet - we are still working through reported bugs from previous releases and hope to fix as many as possible before the final release of 1.7. To be notified when there is a new beta please press follow on this announcment thread
With all that said, we hope that you will enjoy the new capabilities introduced in this initial release and we look forward to any and all feedback you give to us.
Many thanks,
Matt
 
Please refer to previous beta 1.7.0.4 post where there's a list of major changes since 1.6. This latest update builds on the 1.7.0.11 changes and also includes the following changes:
Adopt GPU acceleration (if your Mac supports it) for brushing - automatically enabled, but can be turned off in Preferences New samples! (actually, that'll be in the next build, sorry!) Improved selection logic for small objects and users with tablets Fixed order of palette import/export so it is not reversed! Miscellaneous Metal view mode improvements Fix for 'Create artboard' checkbox in the New Document dialog being incorrectly checked Fix for incorrect arrowhead previews in the drop-down list Restored original context menu behaviour of the Gradient Tool Fix for issues with horizontal or vertical lines not acting correctly in Node Tool Miscellaneous small fixes

Now that Publisher has image linking as it is supposed to be I guess we won’t have to wait for too long to see this feature in Designer as well. To counter the possible argument about how that is of any importance for an app that deals primarily with vectors: here comes a screenshot …

@Matthias , @postmadesign, @mac_heibu ,
@mkaneshiro, @SillyWalk , @fde101, @Jens Krebs, @>|<
Build 326 initially released in this thread has been withdrawn
Please download the replacement build 330 from the link above

Also I figured out why I thought the object disappearing was a bug... it's because the whole area is the same color and appears to be a giant pasteboard, so I'd expect I can use that entire area. Compare this to InDesign (attached screenshot) where the pasteboard is a separate color (white) from the parts that are off limits. It's quite clear the space you have to work with. So my suggestion would be to make this more clear in Publisher as well.