Double check your InDesign Color Setting's Conversion Options (check Advanced Mode). It looks from your screen capture that Black Point Compensation might be unchecked. InDesign and Photoshop appear to handle conversion options differently when converting CMYK back to RGB for display. Here are your swatches as SWOP in ID and PS with ID's Black Point off and a Perceptual rending intent: And with BP on and a Relative Colormetric rendering: ... View more

Cool—too bad it only works for page items and not pages. Rob, you know your identity has converted to doppelgangerland? Had that happen a few months ago and thought I had fixed it—can't see it happening from inside my account. ... View more

I'm not running 5.5 yet, but it looks like the PDF/X-4 preset has been renamed [PDF/X-4:2010] from [PDF/X-4:2008], so you should be able to open the script in ScriptEditor and find the line: set myPDFPreset to "[PDF/X-4:2007]" change it to set myPDFPreset to "[PDF/X-4:2010]" click Compile and save. ... View more

For anyone interested in this script, I made a few changes this morning that should make it run a bit better. I've updated the script and readme at the original address: http://www.zenodesign.com/forum/PagestoPSLayers.zip It no longer asks for a PDF preset—it uses PDF/X-4 for the export. The main reason for using a preset in the earlier version was to include crop marks for registration of the layers, but the new version solves that problem. PDF/X-4 also makes it easy to match color between ID and PS—just make sure Photoshp's color Working Spaces match the ID doc's profiles. I've tested the new version in both CS3 and CS5. ... View more

This is a Quick-and-So-Very-Dirty-Dirty-Dirty javascript I haven't try your code but does JavaScript give you access to a PNG export format that isn't available with the UI? I'm not seeing it in the AppleScript dictionary. ... View more

See if this works. http://www.zenodesign.com/forum/PageToPSLayersCS5.zip ... View more

I think the problem is with opening in 10.6.7. I'll try and post a fix later this afternoon ... View more

I've been running it out of CS5/10.6.4 successfully. What version of OSX are you running? It sounds like the file is never opening in Photoshop. Could you open the script in AppleScript Editor, run it, and then click the Replies button and copy out the error message? ... View more

This is for CS5, but probably works back to CS3. Shows a dialog for choosing resolution and anti aliasing,  asks for a destination folder, and writes the pdf and pngs to that  folder. http://www.zenodesign.com/forum/IDpagestoPNG.zip ... View more

Also, there's no way to "delete" the paper/page/white-background in Acrobat Pro before saving as PNG. When you export the PDF from ID make sure it includes live transparency (i.e., PDF/X-4 and not PDF/X-1a), then the document's page background will be transparent when you open it into Photoshop. Saving pages out to PNGs is scriptable—I have an AppleScript that would work if you’re using OSX. I'm not sure why a PDF page would take minutes to open unless you are asking for huge res—my script opens a page at 300 ppi in a few seconds. ... View more

You should be able to make the squares in a smilar way without the overhead of thousands of display objects via fillRect: import flash.display.Bitmap; import flash.display.BitmapData; import flash.geom.Rectangle; //A white 400x400 pixel canvas var myBitmapData:BitmapData = new BitmapData(400, 400, false, 0xFFFFFF); var bm:Bitmap = new Bitmap(myBitmapData); addChild(bm); var sc:uint=0x000000; //coordinate object var o:Object=new Object(); o.x=100; o.y=100; o.w=30; o.h=50; //fill a rect myBitmapData.fillRect(new Rectangle(o.x, o.y, o.w, o.h), sc); o.x=150; o.y=200; o.w=20; o.h=20; //another fill myBitmapData.fillRect(new Rectangle(o.x, o.y, o.w, o.h), sc); There's also getPixel, which returns the color of a pixel at any x, y, so maybe you could randomly check a pixel and if it's white, check to the left and right and up and down until you hit black, which would give you a rectangle of white to add a randomly sized black fill. ... View more

Do the squares really need to be display objects? Why not make a bitmap canvas and then use the bitmapData fillRect or draw methods. ... View more

when viewing on screen everything is SO dark - many of the images you can't even make out. The Color Setting's Conversion Options can have an effect on the conversion to CMYK even when the colors are in gamut. Unchecking Use Black Point Compensation with a Relative Colormetric intent will often produce a darker separation than a conversion with black point checked. ... View more

http://www.zenodesign.com/forum/PagestoPSLayers.zip ... View more

All your variables are coming up as 0s. ... View more

Seems to work for me on this multiple (3) monitor mac... I get NaN as the zoom value in OSX10.6.4 ... View more

Acrobat displays fairly close to 100% for me. For you but not for everyone. There's nothing universal about 99 —the Apple 27" runs at 109, 15" MacBook Pro at 110, MacBook Pro 17" at 133, ViewSonic VX2433 24" at 92. ... View more

Take a look at Acrobat. An inch displays accurately on my Apple screens running at or near 100 ppi, but not on my laptop running at 115ppi or my old iMac running at 86 ppi. The Acrobat UI designers chose to draw an inch as 99 pixels rather than 72 at 100%, but it still is a fixed number displaying on variable screens. ... View more

All-in-all, this is probably a bad idea to do and I would not recommend it. Oh yeah, and how to undo it: No kidding, resampling (blurring) the interface is not a solution to this minor problem. ... View more

Even though my screen is supposed to be 23" Measure it? I think having the percentages displayed by InDesign accurately reflecting true physical dimensions is just as much a part of people's expectations as being able to view something size as. I can't find an application on my machine with a ruler interface that does that—AI, PS, ID, Word, Pages, Text Edit, Acrobat, Quark. ... View more

http://www.zenodesign.com/ftp/printpreview.zip ... View more

How does ID choose the default it does now? Actual Size sets the zoom to 100% and in that case 1" on the ruler equals 72 pixels—the size of those pixels varies depending on your monitor setup. Surely it doesn't assume a 15" monitor There's no assumption about the monitor size or screen res variables, that's why the display of 1" is variable among different configurations. Why couldn't ID work out of the box just as it does now -- and have a preference for input of user defined screen resolution? Do you really see that as problematic? I think it could be done but as I've said the default would be problematic for many users. I can imagine that Adobe's engineers are reluctant to bloat the prefs file when the problem can be solved with a simple script. I thought all I had to do was to save the copy as a text file with an .as or .scpt extension. No you have to use the Script Editor app. Open Script Editor, paste the code into a new window, click the Compile button and save it with scpt ext into your ID Scripts folder. ... View more

While the script may be fairly simply, isn't that solution something that has to be used every time you open InDesign? No, you assign a key command to the script so you can set the view anytime you want. You could assign Command-1 to the script rather than the default Actual Size menu item. ... View more

Isn't that the current situation? I find it difficult to believe that someone using InDesign wouldn't know the size of their monitor or its effective resolution and find it fairly easy to adjust the value to get the display result that suits them. If the default were 15" and I never changed it, the "Print Size" percentage on my 23" running at 1920x1200 would be 210%—that's what I meant by wildly. Also, the JavaScript that Marijan posted doesn't work on OSX, probably because it's looking for the display res and can't get it from the OS, so it may be on OSX the preference would need to also include hres, vres and the physical dimension. This AppleScript works with OSX: --This works for a Apple 23" Cinema Display change as needed --the display's horizontal and vertical resolution in pixels and monitor's diagonal view area in inches property hres : 1920 property vres : 1200 property diagonal : 23 tell application "Adobe InDesign CS5" activate set printsize to round (((((hres * hres) + (vres * vres)) ^ 0.5) / diagonal) / 72) * 100 set properties of active window to {zoom percentage:printsize} end tell ... View more

So while it may not be perfect, and it may not work for every computer equally, it still seems fairly easy to implement a preference that would help people get what they wanted to see on screen. If we agree that the preference would have to ask for a physical dimension of the monitor, what would the default be? With monitors ranging from 12" to 30" any default would produce wildly inaccurate results on a high percentage of displays. So what you're saying is that there can be no easy fix. Or at least a fix that universally works The posted script is an easy solution ... View more

I don't even know if the current resolutions of monitors are optimal. Maybe in the next 10 years the average monitor will be 150 ppi. If you increase the monitor resolution the displayed pixels get smaller and so the interface also is reduced in size—dialog boxes and text would be reduce by 65% if the display went from 98ppi to 150ppi. ... View more

Am I to conclude the universal use of 72 dpi comes solely from those ancient Macs? I have 3 monitors on my desk manufactured by Apple—23", 20", and a 13.3" laptop. When they run at their native resolutions, which is the default in OSX, the actual pixels per inch for the three are 98.44, 99.05, and 113.49 respectively. I can also choose a non native res and the OS will resample the display (and blur the interface) and I get another set of displayed resolutions. I think the interface designers could choose something other than 72 as the assumed res, but the problem wouldn't go away–98.44 wouldn't work on my laptop. and my assumption of how easy it would be to have a preference for screen resolution The formula for adjusting the zoom percentage needs the display's physical dimension as well as the screen's pixel resolution. A preference would have to ask the user for that dimension. Does the user know it's the diagonal? My 13" MacBook Pro actually measures 13.3" diagonally. What would the default be? Especially when the capability to adjust resolution is acceptable (and easily implemented) in applications such as Photoshop? Photoshop does have a View>Print Size, but suffers from the same problem. When I set the view to Print Size on my 23" screen a displayed ruler inch measures .75". If I have a 275 ppi image I can use Marijan's javascript formula and replace 72 with 275 and get 36% as the percentage, which display's the rulers accurately—the Print Size setting gives me 26.1%, which is not accurate. ... View more

But this leaves me with a question: what exactly is this magic number 72? The first Macs had builtin screens with a res of 72ppi—the mac plus 9", 512×342. When monitors became seperate items driven by third party graphics boards, the screen res became variable. If you are designing a GUI for InDesign that shows rulers you have to settle on how many pixels there are in an inch when the zoom level is at 100%. In InDesign it's 72 pixels, in Photoshop it's the image's ppi. The size of the displayed pixels changes depending on the monitor capabilities—if you could find a screen running at 72ppi, ID's 100% zoom would show ruler inches measuring exactly an inch. Dividing by 72 gives you the ratio that compensates for the actual screen ppi and the assumed 72ppi. In case you thought there would never be a practical use for your long forgotten high school algebra, Marijan's javascipt channels Pythagoras to get the actual screen res, where your screen's diagonal is the hypotenuse. ... View more