I'm not going to pretend to be able to explain why this is working the way it does, but it's the result of new code that queries your monitor for the ACTUAL resolution it is using and then displays a 100% view at a real 100% size, at least in theory. Apparently it doesn't work correctly in Windows 7, but it is supposed to be accurate on Mac, and there's a pretty good chance that if you spec a page in something other than pixels and hold up a ruler to the screen it will be pretty darn close.
ID uses a 1:1 correspondence between points and pixels on the ruler, however, and as there are 72 points/inch that means you are designing at 72 ppi when you spec pixels, even though ther probably isn't a monitor on the planet outside of a museum these days that actually uses 72 ppi internally. if you divide your pixel dimension by 72, and hold up a rule to the screen, does your page measure correctly in inches?
This is obviously an embarassing omission on Adobe’s part, especially given the recent push for InDesign to be used as a web design tool. The problem was successfully solved in Acrobat, where "actual" user resolution can be set as a user preference. Even better would be for it to be document type relevant (ie default CS6 behavior for Print, 72dpi for Web).
A quick and dirty trips from the smart minds at IDS allows us to keep working in the meantime:
OK, I found a two-line script that John Hawkinson wrote that will get you back the old display zoom factor at 100%:
app.generalPreferences.customMonitorPpi = 72;
app.generalPreferences.useCustomMonitorResolution = true;
When you want to switch back again to accurate 100% view run this:
app.generalPreferences.useCustomMonitorResolution = false;
That worked for me. Thanks!
This is truly, completely, insanely, incomprehensibly, and unfortunately, TYPICALLY Adobe. I wish with all my heart they didn't have a monopoly on creative tools the way they do. They are the Microsoft of Creative tools. Look at us, we have to do terminal style code changes to make a product look the way it should?! THIS IS CRAZY! Adobe is trying to enter the epublishing market with an app that give you the wrong pixel sizes on your screen? Ohhhhhhhhh/ Myyyyyyyyyyy. Woooooooooord! Adobe, ADOBE! Are you listening?! Stop it.
If you are still reading. Let me offer a word of advice: We want the power of In Designs grid and guide creation, BUT can we have the simple, pathetically-normal-to-expect ability to have new objects snap to pixels?!!? I know this looks like a teenager wrote it, with excalmation marks, un restrained exasperation and ALL CAPS, but i'm just finished. I draw a square, the edges are fuzzy. I have to go to the inspector and nudge the 0.5 px off the square. Even then, it soemtimes doesnt do it. Can you image the scenario that MAYBE UI AND UX designers would like to have, oh I dunno, WYSIWYG!? I'm trying to figure out what is going on through your heads when you're designing a program with UI UX designers i mind, technally, it's being made by, oh i dunno... UI/UX designers?!? But the funny thing is, the adobe interface is beautiful. How on earth did you design that with blurry lines all over the place?
Have you seen how type renders in Indesign at "Actual Pixels"?! Have you seen how the elegant forms of Helvetica Neue which we all know so well is output to look like it's done a bag of Ketamin? Shame on you. For reals, shame on you. These are things that your users NEEED. We need to see things as they will look. It's call attention to detail. It's like designing in the dark with you guys.
Please dont tell me what a true pixel is. That is the most retarded thing i have ever heard, you will lose users in droves. Oh wait, where will they go to?! Nowhere! You are all they have! Nice one Adobe! But watch out you have pixelmator nipping at your feet. Soon your super overpriced stinking business model and your dicatative havent-got-a-clue, disrespectful to common se