pixel preview doesn't refresh correctly until reapplied.
Steps to reproduce:
- New document with units set to pixels
- view: 'snap to pixel' and 'pixel preview' turned on.
- Use the rectangle tool to make a new shape, eg. 20 pixels square.
- Set the fill colour to a high contrast colour (eg. dark grey) and turn off the stroke
- zoom the view, move around.
Expected result:
- the rectangle should appear pixel-perfect (sharp) against the pixel grid, with no anti-aliased bluring
- the view should acurately update when I zoom and move around to display pixel perfect artwork
Actual result:
- the rectangle is bordered by a blured anti-aliased semi-transparent edge pixel, and does not appear pixel perfect
- if I re-toggle 'pixel preview' then the pixel-perfect effect comes back, but I shouldn't need to do this.
-
Ah, Mark, that is very kind of you :)
And I can’t but agree with it :DThere any many users here like me here, who try to help AI to get better (or just suffer and want it to be fixed), and some do their part at the Adobe forums and in various communities. You are one of us, so thank you for the heads up. Let’s hope that UV will make a change.
(Edited by admin) -
Mark Nicoll commented
Ok, good to know, thanks.
Incidentally, I'm very glad you're now an admin here. I've always appreciated your broad knowledge and focus, and thought if would be a good thing if Adobe had you on board :)
-
No, Mark, it is not. It’s a side-efect of this, and the team is aware of it and searches for the solution.
It’s all about the resolution and assumption that 1 inch has 72points in it, the legacy resolution Ai has no ways to customize. This leads to 100% on print displayed wrong, so an option was made to make it look right... which breaks pixel preview. At least you are aware now :((Edited by admin) -
Mark Nicoll commented
Egor - yes, it does.
Are you saying the current behaviour (without that workaround), where it displays haphazard anti-aliased edges, is intended?
-
Yeah, it does. Try to disable 'Display Print Size at 100% Zoom' in Preferences as a workaround. Does it fix that?