Jump to content

Search the Community

Showing results for tags 'afp-2418'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests, Suggestions & Discussions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. I have a personal palette that combines the standard greys and colours into a single palette called David Mac. This I have exported and saved as DavidMac.afpalette When AP opens it opens always to the Grey palette. If I then select my own DavidMac palette from the palette dropdown list it displays just as it should. If I then set this as the RGBA/8 Application Default palette in the Swatches menu I receive a message ‘Default Palette Saved’. However if I close Affinity and re-open it defaults once again to Grey. Creating a new RGBA/8 document doesn’t then switch to the DavidMac palette I have saved as the RGBA/8 default - I have to select it again from the dropdown. Now to my naive mind a default RGBA/8 Application Palette is the one that opens automatically by default for any RGBA/8 image, be it an existing image or a new blank image, but this isn’t happening. BTW, although I am posting here because the problem exists in the latest 118 beta release, this is not new to just the beta - it has always behaved thus from the very first AP. So am I missing something obvious here (which I often do) or is this a very longstanding bug?
×