LCamachoDesign Posted December 11, 2023 Share Posted December 11, 2023 Right clicking a swatch created on any document palette created after the first one will no longer have the Edit, Rename and Delete menu entries active. See the image below: Steps to reproduce: Create a new document Create a new document palette, name it 1 for easy reference Create a new global swatch, make it spot to enable the Rename Spot menu too Right click the newly created swatch See that you can edit, rename and delete this swatch Create a new document palette, name it 2 for easy reference Create a new spot global swatch Right click this new swatch, notice the disabled menu items Creating further palettes and swatches Notice the problem continues Video guide below: Swtaches menu.mp4 Thanks! Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted December 11, 2023 Share Posted December 11, 2023 Thanks for the recipe. Sounds like it might be the same problem mentioned by another user here: LCamachoDesign 1 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
Staff Callum Posted December 12, 2023 Staff Share Posted December 12, 2023 I have logged this to be fixed in a future update Quote Please tag me using @ in your reply so I can be sure to respond ASAP. Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted January 3 Staff Share Posted January 3 The issue "Can't edit colours in second document palette" (REF: AF-1545) has been fixed by the developers in internal build "2.3.1.2212". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.