AP Can't get default swatches to work.

[DavidMac]

AP on Mac OS Mojave

This something I first reported years back in the very, very early days with first release of AP. Nothing has changed since then so I am tempted to believe that I may be failing to understand something rather than there being a fault in the app.

I find having to keep switching greyscale and colour swatches rather tedious.  So I created a swatch of my own that contains both greyscale and colour in a single swatch palette. It is set as an application palette. I saved this and on startup can select it in the palette drop down just above the swatches. So far so good.

However the swatches menu has an option "Save as default", followed by the colour modes for which you would like it to be default. I set my new palette to be default but AP ignores this and always defaults to the grey scale palette. Now maybe I am misunderstanding but, to my simple mind, a default palette is the one that loads on startup. However I cannot get any palette, including the AP native palettes to load as default in any colour mode. I have tried every combination I can think of but AP resolutely insists on always starting up with the greyscale swatches. 

I cannot believe, after such a long time, that this can be broken. If that were the case then plenty more users than I would surely have reported it right from the early days just as I did, so I have to presume that somewhere I am missing something - I am often rather good at that.🤔

So what am I missing to get this feature working or am I misinterpreting entirely the meaning of "default".

[Dan C]

Hi @DavidMac,

I'm sorry to hear you're having trouble. My apologies for the delayed response here, we are extremely busy following our 1.10 update and working from home during the pandemic is unfortunately extending our response window to be longer than normal, many thanks for your continued patience and understanding here!

I can confirm that unfortunately this is a long standing bug within the application, that I have confirmed still exists in 1.10.

This bug is logged with our developers, so I will be 'bumping' this report now and updating the affects versions to include 1.10 on Windows and Mac - hopefully this will bring the issue to the attention of our devs once again.

I hope this clears things up!

[DavidMac]

Thanks Dan. No apologies needed. I know the last two years have been very difficult for you all. This is not let's face it a serious bug, which is why I hadn't pursued it for so long. It's easy enough to import my palette when I start. It's just one of those minor irritations one would prefer not to have. Hopefully next version. 🙂