Search the Community
Showing results for tags 'apl-479'.
-
I've been working on creating an extensive palette. My normal process is to create an object, set the colour in HSL, then create a global swatch in a document palette. I will often go back and tweak the global swatch. I've built up a hundred or so swatches this way. Now, the method for adjusting a global swatch is a bit cumbersome. A lot of clicking and re-clicking, selecting, deselecting, etc. The whole swatch panel and handling of global/spots is a bit of a pain, to be honest. I've decided it would actually be easier if I didn't set swatches until I was 100% happy with the colours and want to lock them in. Now, I've got about 180 objects set to global swatches that I want to detach back to HSL values. Normally this can be done by right clicking a swatch and deleting it. But I don't feel like doing "right-click, click delete colour, click yes" 180 times. So I tried deleting the document palette, hoping it would detach them all at once. It didn't. They are still global swatches that technically don't exist anymore. At least as far as the swatches panel is concerned. Is there an easy way of detaching all the objects to HSL at once? I don't want to have to individually select these objects and eyedropper them back to HSL one by one. side comment: when I copy-paste an object using a global swatch from one document to another, the global swatch is there but doesn't appear in any document palette. I'd rather the swatch be automatically added, which is how InDesign and Illustrator behave. Right now, I'd have to manually add it as a new global swatch and rename. Again. Defeating half the purpose of creating a global swatch in the first place. And why when you export a palette then import it as an application palette do they lose global swatch functionality? Also defeating the purpose of having global swatches. I work in print where setting spot/global colours and drawing from colour books is a common and necessary process. I don't understand why it works this way.
-
Preface: I'm working simultaneously on different screendesign- and printdesign documents (RGB vs. CMYK) side-by-side. Ergo: I have the padlock "colourspace lock" deactivated so I don't have to remember to manually switch every time I click into the other document when I do stuff with the colour panel. I also can copy a coloured object from the CMYK doc to the RGB doc and it retains its original colour values. I can inspect this in the colour panel: click on RGB object -> RGB sliders, click on CMYK object -> CMYK sliders. (CHECK) This works fine until I have a CMYK global colour: the object is copied over correctly from the CMYK to the RGB doc, but when clicking on <EDIT GLOBAL COLOUR> it displays the popup with whatever sliders were selected before, as if It had checked the lock internally with no way to disable that, because there is no UI for it. Thats an easy trap for unwanted colour changes. I want to be able to inspect which colourspace a particular swatch (global) was created in. And: Yes I know that RGB colours will look different when used in a CMYK doc. I just want it to retain its original creation values (for later use in a CMYK doc.) Please fix this, maybe by adding this lock also to the popup. (and please make the ON/OFF state more visible.) Bildschirmvideo aufnehmen 2021-05-21.mp4