Lance
My feedback
243 results found
-
4 votes
Lance supported this idea ·
-
14 votes
Lance supported this idea ·
-
115 votes
Lance supported this idea ·
-
5 votes
Lance supported this idea ·
-
5 votes
Lance supported this idea ·
-
3 votes
Lance supported this idea ·
-
30 votes
Lance supported this idea ·
-
7 votes
Lance supported this idea ·
-
4 votes
Lance supported this idea ·
-
4 votes
Lance supported this idea ·
-
7 votes
Lance supported this idea ·
-
14 votes
Lance supported this idea ·
-
2 votes
Lance supported this idea ·
-
2 votes
Lance supported this idea ·
-
5 votes
Lance supported this idea ·
An error occurred while saving the comment An error occurred while saving the comment Lance commented
I am unable to reproduce this in my Illustrator installation.
-
178 votes
Lance supported this idea ·
-
5 votes
@enisio We are able to reproduce this issue with the steps you provided. Thanks for not letting this go
Lance supported this idea ·
-
5 votes
Lance supported this idea ·
An error occurred while saving the comment Lance commented
This *looks* like an RGB -> CMYK conversion, but the document's tab claims the document itself *is* RGB mode.
Voting for what appears to be a legitimate bug.
-
2 votes
Lance supported this idea ·
-
5 votes
An error occurred while saving the comment Lance commented
I agree that the behavior here looks odd, but only when the black object uses a lowered opacity instead of a tint. I'm not sure what the utility of overprint is in this instance though, or why it would be used in addition to a blending mode.
If you don't use the opacity and instead use tint, or just stay out of overprint preview mode then there's no issue.
Eugene, Ton -
I still can't replicate this, even with a fresh document. Doesn't affect my installation at all whether the spot color is custom, or pantone. I did briefly see the object flicker back to visible but it didn't stay visible. Looked like a slight lag in the rendering.
Am I missing something?
*** edit, leaving above for posterity ***
I incorrectly assumed "non printing" meant "hide the layer" or "layer visibility turned off" rather than set the layer's properties/options to be a non-printing layer.
It didn't initially cross my mind to try that because that's an option that I knew of but have never used for any reason.
Easily reproduced using that option. Agree that it's very strange and probably unintended behavior.