AffDes v2.0.3-File New-default colour palette does not show

[catlover]

Hello, due to health issues I haven't been able to participate in the forum for a while. I wish everyone a very happy and above all healthy new year.

My problem: Ever since installing v.2.03 of AffDes, upon File>New the default colour palette does not come up. Instead I get a colour palette that I made a long time ago, namely "Autumn". This is the first palette in the list. Even after deleting this palette and choosing the default "colours" palette > File New> it still reverts back to the first palette in the list, whatever that particular palette may be. I've tried deleting several palettes,"set as default for...", checked preference settings etc., but it does no good.  I suspect something went awry with the automatic transition from v1 to v2, so I tried finding the palette propcol file. Unfortunately couldn't find it. 

Help will be very much appreciated. Thank you !

PS: I've had to change the forum settings and don't seem to be able to get the preferred contents back. So please send me a PM, which I will check for regularly.

 

[Pšenda]

11 minutes ago, catlover said:

"set as default for...",

And "Remove as default for..."?

[catlover]

Thank you, I tried that just a minute ago - didn't work. Removed as default for, then set as default for.

I still get the first palette in the list when choosing "file new".

I still have v 1 installed, there it works as expected, even with both apps running.

[R C-R]

2 hours ago, catlover said:

Thank you, I tried that just a minute ago - didn't work. Removed as default for, then set as default for.

I still get the first palette in the list when choosing "file new".

FWIW, on my Mac setting a default for any of the color spaces in V2 does not seem to work ... or I do not understand how it is supposed to. Seems like a bug to me.

[catlover]

@RC-R : Yes, I think you're right : a bug. Let's hope that in time it will be ironed out.

I don't think I'm the only one having this problem. 

[R C-R]

1 hour ago, catlover said:

@RC-R : Yes, I think you're right : a bug. Let's hope that in time it will be ironed out.

I don't think I'm the only one having this problem. 

Are you a Mac or Windows user, & which OS version do you use?

[catlover]

I'm on Mac, IOS Big Sur v 11.7.2.

[R C-R]

16 minutes ago, catlover said:

I'm on Mac, IOS Big Sur v 11.7.2.

I'm on macOS Catalina, so I wonder if this is a Mac-only problem. maybe a Windows user can confirm here if it is working as expected for them?

[lacerto]

IMO the feature works similarly as it has always worked, both on Windows and on macOS, and both with v1 and v2 apps.

That is, the "default" simply just loads the specified palette as a working palette at document creation time. It does not activate the palette so that it would be selected when the document is created (instead, the last used in-built or application palette would be active).

The best use of this feature would be creating a custom palette e.g. with some often used color definitions (e.g. named corporate colors, overprint and knockout versions of black, standard rich black, spot colors, etc.) defined as a document palette so that global color definitions could be used, and then specifying it as a default for e.g. CMYK/8 documents:

[jmwellborn]

@catlover  since the palettes are now arranged alphabetically, a very simple way to make your Default palette always appear at the top of the list is to rename it:  AAA Default.  Sort of a clumsy solution, but it would work!🙂

[Pšenda]

1 hour ago, jmwellborn said:

AAA Default.  Sort of a clumsy solution, but it would work!🙂

If you would mind a name with the initial letter A, which does not correspond to your naming, I recommend using "_" (for example _My Palette).

[R C-R]

3 hours ago, lacerto said:

That is, the "default" simply just loads the specified palette as a working palette at document creation time. It does not activate the palette so that it would be selected when the document is created (instead, the last used in-built or application palette would be active).

How is loading this "default" palette any different from loading all the others? Aren't they all loaded into the app at startup? Regardless, what is the point of setting a default palette if it does not automatically become the selected one when creating a new document?

The help topic is not of much help with this. For AP V2, it just says:

 

Quote

 

Setting default palettes

Any palette can be set as the default used for specific colour formats. For example, you can set RGB/8 documents to have a different default palette to CMYK/8 documents.

 

 

[lacerto]

8 minutes ago, R C-R said:

How is loading this "default" palette any different from loading all the others? Aren't they all loaded into the app at startup?

1) Whether a palette is loaded, depends on the color mode. This allows to optimize to some extent print-specific, gray and digital media palettes.

2) By specifying a palette as "default", you can work around the limitation of application-wide palettes not having a capability of having global swatches (and accordingly, parents of tints, and have an overprint attribute). [That is, the "default" feature allows document palettes becoming kind of color mode specific application palettes.]

[R C-R]

1 minute ago, lacerto said:

1) Whether a palette is loaded, depends on the color mode. This allows to optimize to some extent print-specific, gray and digital media palettes.

??? AFAIK, all the palettes are loaded into the app when it starts up. At least there is zero detectable delay when changing palettes, so I think they must already be in memory.

[lacerto]

12 minutes ago, R C-R said:

??? AFAIK, all the palettes are loaded into the app when it starts up. At least there is zero detectable delay when changing palettes, so I think they must already be in memory

The point is that "default" palettes can behave like document palettes when creating a new document. Application palettes do not have capabilities of document palettes (as mentioned above).

[R C-R]

35 minutes ago, lacerto said:

The point is that "default" palettes can behave like document palettes when creating a new document. Application palettes do not have capabilities of document palettes (as mentioned above).

How exactly are they behaving as default palettes for new documents? Any palette cn be used simply by selecting it from the popup but like you said, when creating a new document whatever palette was last set is the one you start with.

So again, what is the point of setting a 'default' palette if it is not automatically selected when a new document of a particular color format is created?

[lacerto]

12 minutes ago, R C-R said:

How exactly are they behaving as default palettes for new documents? Any palette cn be used simply by selecting it from the popup but like you said, when creating a new document whatever palette was last set is the one you start with.

I have tried to explain this above. But try to create a custom palette that behaves like a document palette so that you can have global swatches included (they are needed to be able to apply Overprint attribute, and to be able to create parent-child tint relationship). Application-wide palettes cannot have global swatches.

It would be useful if Serif improved the feature so that the user-defined default palette would also be automatically selected as the active palette whenever creating a document with a specific color mode. Perhaps this happens one day, but I'm not holding my breath. 

[walt.farrell]

53 minutes ago, lacerto said:

But try to create a custom palette that behaves like a document palette so that you can have global swatches included (they are needed to be able to apply Overprint attribute, and to be able to create parent-child tint relationship). Application-wide palettes cannot have global swatches.

Correct. You could, of course, create a Template with your Document Palette in it, and start new documents using that Template.

[R C-R]

1 hour ago, lacerto said:

I have tried to explain this above. But try to create a custom palette that behaves like a document palette so that you can have global swatches included (they are needed to be able to apply Overprint attribute, and to be able to create parent-child tint relationship). Application-wide palettes cannot have global swatches.

Sorry, but I still do not understand what this has to do with setting a default palette for new documents. What does "default" mean if not a preselected option?

[,,,]

15 minutes ago, walt.farrell said:

Correct. You could, of course, create a Template with your Document Palette in it, and start new documents using that Template.

Does that make any difference on Windows?

On Mac, the app's last used palette (or the first Application Palette in the list when the app has only just launched) is selected when a new document is initialised from either a template or an app document preset.

[lacerto]

28 minutes ago, walt.farrell said:

You could, of course, create a Template with your Document Palette in it, and start new documents using that Template

I would rather define a few default palettes and have them available with any kind of document (disregarding the format etc.), possibly with just color mode specific variations, than creating various templates using different formats just to have a standard palette available.

Interestingly default palettes do not seem to be loaded with a template based new document (of the defined color mode). Perhaps this is a bug (only tested v2 apps on Windows for this feature).

[lacerto]

13 minutes ago, R C-R said:

What does "default" mean if not a preselected option?

I think it is a poorly selected term. But perhaps the palette was designed to be activated, too, but the feature just is not properly implemented.

[walt.farrell]

Just now, lacerto said:

I would rather define a few default palettes and have them available with any kind of document

But you can't do that, and get Global colors. You must have a Document palette, and they must be created for each document specifically unless you use a Template.

[R C-R]

1 minute ago, lacerto said:

I would rather define a few default palettes and have them available with any kind of document (disregarding the format etc.), possibly with just color mode specific variations, than creating various templates using different formats just to have a standard palette available.

Can't we do that now? Every system or app level palette I have created or ships with the apps or is linked among the V2 apps is available from the popup menu.

[,,,]

12 minutes ago, R C-R said:

What does "default" mean if not a preselected option?

A default pre-populated Document Palette for new documents of a given colour format, such as RGBA/8.

Unless you set such a default palette for a particular colour format, new documents of that colour format will have no Document Palette.