Use same global colors in personas?

[Nathan Shirley]

I have a Publisher project with linked Designer files. Within the Publisher project I have setup custom global colors. If I edit one of the Designer files in Publisher (using the Designer persona) my global colors are not available. I could add new global colors within the persona, but I'm afraid that might not allow me to change those colors in the future if I decide to adjust a global color within Publisher. Is this possible somehow?

[thomaso]

To use a global palette in various files you could export + import the palette again and again.
Another, some more cumbersome way could be to create a set of colored objects, copy/paste them and re-create their global palette in the other document this way.
However, both ways are tricky because you have no control about the state of a swatch (original or changed?), although at least a little control exists if you name the swatches with their values (and rename them with every change).

Unfortunately, there is still no way for a global application palette whose color fields allow you to change their color values.
Also there is no way to copy/paste objects with their global swatches because copying an object doesn't transfer its colour swatch.
It would be a helpful feature at least to copy a range of colored objects and transfer this way their swatches. That could make the current "global" a little more global.

[Nathan Shirley]

Thanks for the information.

2 hours ago, thomaso said:

Also there is no way to copy/paste objects with their global swatches because copying an object doesn't transfer its colour swatch.

Oh no... I was operating with the assumption that copying objects would include all contained global colors... That's going to mean a lot of work manually setting all of these object's colors.

Is there some reason why globally colored objects don't work this way?

[thomaso]

Quite a few of us were expecting a different swatches and palettes handling, in particular for global colors, and there are quite a few threads about it in the forum. - I assume Serif had a reason for this decisions but I can't imagine yet a purpose or a users use of it.

Besides the mentioned export/import of the palette: As another workaround you could copy/paste all the Designer objects into your APub document (and kick the linked items *). That way you can assign the colours from your global APub palette to the Designer objects by select & click – instead of repeating the swatch creation procedure again, or to avoid confusion with export/import of the palette once a color has changed.

* Unfortunately even embedding the placed Designer files doesn't make their objects to become APub objects, so embedding doesn't enable you to assign the global colours to these objects. Even embedded they are still separate documents, without access to the palette of their mother container, the .afpub.

[Nathan Shirley]

Interesting, hopefully Serif will make improvements along these lines within too long.

[walt.farrell]

8 hours ago, Nathan Shirley said:

I was operating with the assumption that copying objects would include all contained global colors...

Copying an object which has a global color will copy the color as global, if you paste within the same document. But if you paste into a different document it won't be global there. And if you change it in one document the other document won't be affected.

[Nathan Shirley]

Oh thanks for the clarification, that's very good to hear.