Joakim Svensson Posted February 7, 2021 Share Posted February 7, 2021 I love that Affinity Publisher can create System Palettes and share the colors with other applications beside the Affinity suite. But rearranging the colors in a palette has always been sketchy in Affinity Publisher and makes the application crash more often than not. Trying to drag the first color to another position is a bulletproof way to crash the application (other positioned colors are more of a 50/50 risk of crashing). I'm on Affinity Designer 1.9 and MacOS 11.2 (Intel). Let me know if I can provide more information for you to be able to solve this, I'm far behind in my color palette management because of this. example.mov Quote Link to comment Share on other sites More sharing options...
Joakim Svensson Posted February 7, 2021 Author Share Posted February 7, 2021 Same behavior in Photo and Designer as well Quote Link to comment Share on other sites More sharing options...
loukash Posted February 7, 2021 Share Posted February 7, 2021 (edited) 16 hours ago, Joakim Svensson said: rearranging the colors in a palette has always been sketchy in Affinity Publisher and makes the application crash more often than not. What does "always" mean? Can't reproduce with v1.8.4 on El Capitan: Rearranging works for me in both palettes simultaneously. Actually I do use custom system palettes a lot, inside and outside Affinity across apps like Adobe CS or Logic Pro, even syncing them between different Macs and between MacOS versions from Mountain Lion Leopard (!) up to Catalina. Can't comment on Big Sur issues though. Perhaps you may want to upload a document and a palette that crash? Palettes are inside ~/Library/Colors Edited February 7, 2021 by loukash Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2 Link to comment Share on other sites More sharing options...
loukash Posted February 7, 2021 Share Posted February 7, 2021 5 minutes ago, loukash said: Leopard (!) Just checked my backup catalogs, and one of my custom system palettes dates at least as far back as July 2003 – that was on Mac OS X Jaguar! – and its current incarnation was unchanged since 2012 until I briefly tested it right now. The *.clr file format is obviously still the same to this day. Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2 Link to comment Share on other sites More sharing options...
Dampsquid Posted February 9, 2021 Share Posted February 9, 2021 Not even rearranging colours - just adding a new one. As soon as I hit enter after adding a hex value the app crashes. Immediately. Every time. Screen Recording 2021-02-09 at 3.56.46 PM.mov Quote Link to comment Share on other sites More sharing options...
loukash Posted February 9, 2021 Share Posted February 9, 2021 Perhaps an incompatible 3rd party color picker plugin? I've got a few nice ones that still work, like the ~/Library/ColorPickers/SkalaColor.colorPicker (bjango.com/help/skalacolor/gettingstarted). But I vaguely recall that some old ones may have caused troubles. Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2 Link to comment Share on other sites More sharing options...
Dampsquid Posted February 9, 2021 Share Posted February 9, 2021 1 hour ago, loukash said: ~/Library/ColorPickers ^ nothing in that folder here... no plugins in use... Quote Link to comment Share on other sites More sharing options...
Joakim Svensson Posted February 10, 2021 Author Share Posted February 10, 2021 Nothing in ~/Library/Colors I've used different versions of Affinity software across different versions of MacOS and even computers, rearranging System Palettes has always been sketchy for me. Quote Link to comment Share on other sites More sharing options...
loukash Posted February 10, 2021 Share Posted February 10, 2021 20 minutes ago, Joakim Svensson said: Nothing in ~/Library/Colors That's where the color palettes actually should be, regardless which app creates them. What if you create a custom palette via Apple's Color Picker first? Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2 Link to comment Share on other sites More sharing options...
Joakim Svensson Posted February 10, 2021 Author Share Posted February 10, 2021 Sorry, you're right. There was plenty of files in ~/Library/Colors. Here are two copies of the same palette with the only difference that the color names of "Does not crash.clr" have been renamed. "Crashes.clr" terminates the application when shuffling around the two colors in the color palette a few times. "Does not crash.clr" does not. Crashes.clr Does not crash.clr Quote Link to comment Share on other sites More sharing options...
loukash Posted February 10, 2021 Share Posted February 10, 2021 Still can't replicate:crashpalette19.afpubCrashes–really?.clrCrashes?.clr Moved swatches around, added swatches, renamed swatches, renamed palette, both in APu and in Apple Picker. Renaming palette in APu while having it open in Color Picker and vice versa resulted in palette duplication upon relaunching APu, but still no crash. That's on High Sierra. It must be something else on your MacOS installation. There's so many variables… Possibly a specific Big Sur issue? Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2 Link to comment Share on other sites More sharing options...
Joakim Svensson Posted February 10, 2021 Author Share Posted February 10, 2021 Ok, so I made a few more tests. The crashed only occur when the palette contains a color with a name longer than nine characters. When all color names are nine or less characters long it always works flawlessly. I could replicate the error with loukash attached palettes. The problem has been present for me since the first version of Designer (probably before then in the other apps as well. It was not until the first version if Designer started organizing colors this way). As I said, I've been using multiple computers and OS versions. I've been using Skala on prior machines, but not since the developer decided to take a different route and stopped supporting the ~/Library/ColorPickers -plugin. There are no files in that folder. Well, I guess I'll rename the colors to shorter names, that workaround works. Quote Link to comment Share on other sites More sharing options...
loukash Posted February 10, 2021 Share Posted February 10, 2021 34 minutes ago, Joakim Svensson said: stopped supporting the ~/Library/ColorPickers -plugin (Unrelated to your issue, but yeah, I've noticed that it's nowhere to be found for download on Bjango's website. Luckily I always keep at least one latest version of any software I've downloaded backed up. Other than that, I'm an iStat Menus user since many years. Can't work on a Mac without them. iStat Menus and Little Snitch being always the first two things to install on an untouched MacOS.) Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2 Link to comment Share on other sites More sharing options...
Joakim Svensson Posted February 11, 2021 Author Share Posted February 11, 2021 I took some time to organize and rename my clients System Palette's colors to be less than or equal to nine characters long and have not experienced any crashes when rearranging colors since. Perhaps someone at Serif should look into this? I think I narrowed down the problem pretty well. 20 hours ago, Joakim Svensson said: The crashed only occur when the palette contains a color with a name longer than nine characters. When all color names are nine or less characters long it always works flawlessly. Quote Link to comment Share on other sites More sharing options...
Staff Gabe Posted February 22, 2021 Staff Share Posted February 22, 2021 Hi all, Sorry for the delayed reply, We are aware of this and it has already been logged with our developers. 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.