Permanent zoom level within Reading pane

Folks
I found a way to set the zoom level permanent if one opens an email message in its own window. However, I can't find anything for the reading pane. Does anybody know how to set the reading pane to 110% for all messages, even if close and open Outlook?
http://www.slipstick.com/outlook/adjust-outlooks-zoom-setting/#comment-183349
Thx

Hi,
We can not make the zoom change permanently for Reading Pane on Outlook side, but you can try to find some third-party add-in to achieve the goal.
As a workaround, we can convert HTML messages to Plain Text and then customize the font size for Plain Text messages. For more information, please refer:
http://www.msoutlook.info/question/67
Hope this helps.
Regards,
Steve Fan
TechNet Community Support

Similar Messages

Is there a default setting for the Preview Pane Zoom level?

I want to have my default zoom level of my preview pane set to "Fit to Window"
Mine is default set to 100%. This is too big. I can not find the option.

Select the audio clips and use Modify>Stereo Pair. Command- period.

How do I permanently set the zoom level? I am sick of hacing to "ctrl +" on every page!!

How do I permanently set the zoom level? I am sick of hacing to "ctrl +" on every page!! It is a HUGE waste of time. If I can't do it, then no more FF.

The Firefox [https://support.mozilla.com/en-US/kb/Page+Zoom Page Zoom] feature does a domain by domain level of saving the users preferred zoom level settings, there is no default Page Zoom level setting in Firefox, as with some other browsers.
Try the Default FullZoom Level extension: <br />
https://addons.mozilla.org/en-US/firefox/addon/6965
Or the NoSquint extension: <br />
https://addons.mozilla.org/en-US/firefox/addon/2592/

How to fix pages zoom level permanently in FF8 ?

I have 15,6 " laptop with Full-HD resolution. Therefore, by default all text is too small to read. In Windows 7 and in IE there is a possibility to set zoom to 125% permanently, and this fixes the problem.
In FireFox the text becomes readable if I click CTRL+ two times. But this CTRL+ affects either to one tab or to one website only. But how can I permanently fix this zoom level (CTRL+ two times) in FireFox for forever ?

You can use 1 of these add-ons :
https://addons.mozilla.org/en-US/firefox/addon/nosquint/
https://addons.mozilla.org/en-US/firefox/addon/default-fullzoom-level/
for me nosquint is excellent choice
thank you
Please mark "Solved" the answer that really solve the problem, to help others with a similar problem.

Can I tell at server-level if a message has been displayed in the Reading Pane in Outlook?

Hello,
Does anyone know if there are any traces at server-level (Exchange 2010) if a message has been displayed in the Reading Pane of Outlook 2010? The message would still be marked as Read in the recipient's mailbox.
Thanks,
- Alan.

Hi,
If you want to know whether an email has been read by recipient, you can either request a read receipt or enable the tracking for read status for messages by using the
Set-OrganizationConfig –ReadTrackingEnabled:$True command.
A related blog for your reference.
Question: Is it possible to check if a message has been read, even when the sender forgot to check the box “Request a Read receipt for this message”?
http://blogs.technet.com/b/ilvancri/archive/2010/04/13/question-is-it-possible-to-check-if-a-message-has-been-read-even-when-the-sender-forgot-to-check-the-box-request-a-read-receipt-for-this-message.aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Unresolved bug in adobe reader x with non-default windows zoom level

This seems to have already been brought up here about a year ago: http://forums.adobe.com/thread/776060.
I am using Windows 7 Professional 64-bit with Firefox 12.0 and Adobe Reader 10.1.3. Here is a description of the problem:
Whenever I open any PDF file in a browser (firefox or IE) using the adobe reader I am unable to select text, save the file or interact with the content in any meaningful way because the plugin does not recognise my cursor position. If I click on some text in a PDF document, the reader will immediately highlight a region of text between where I clicked and where it thinks I started clicking from (above 20% of the screen above and to the left of where I actually clicked on the page). If I roll my mouse over the region where the dashboard normally appears, the dash does appear as intended and the cursor changes in response to hover over buttons, as if everything were working, but I am unable to click on anything (clicking does nothing). If I click and hold the dashboard when it appears, it immediately jumps to another region of the page, as if it thinks I moved the mouse (20% up and to the left again). I have recently reformatted and am now using a fresh install, and the issue remains. My desktop zoom level in windows is 150%. The problem appears only inside the browser; viewing PDFs directly in Acrobat Reader X works without issue.
I can resolve the problem either of two ways:
a) Reverting back to the default windows zoom level (125%).
b) right-clicking on the Adobe Reader X icon, navigating to the compatibility tab and clicking "Disable Display Scaling on high DPI settings"
The workaround is easy but it's disappointing that adobe hasn't fixed this. Please consider that it would mostly affect individuals who are vision impaired and might not have the know-how to resolve the problem or check for solutions online, let alone post comments such as this. As far as I can tell this problem severely impaires the functionality of adobe in any browser on any non-standard zoom windows installation.

Please be sure to post your issue in the following Feature Request/Bug Report Form.

How can I make a permanent change in the zoom level?

I want to know how I can make a permanent change is the zoom level? I dont want to constantly have to change it from the default value of 100% every time I go to a different page. Thanks.

Hello,
You can also use the [https://addons.mozilla.org/en-US/firefox/addon/2592/ NoSquint] add-on to change the default zoom level for all websites at once. After setting your global zoom level, you can fine-tune the zoom on individual sites and set the options so that NoSquint remembers per-site settings.
After installing NoSquint, go to the add-ons page to set the per-site settings:
* Tools (or [[Image: New Fx Menu]]) > Add-ons > Extensions
* Click the "Options" button by NoSquint

The Reader needs new functionality to remember the zoom level

Let's say you are reading an ebook with a zoom level of 167%, and you decide to jump to a new page from the table of contents. Then you lose the zoom. This is a low level bug and should be fixed by the Abode team. Also the Reader needs forward and backword buttons to facilitate jumping to new pages of the ebook. To sum it up, a lot people are using the Reader as a ebook reader and the Reader is currently lacking some features to support reading ebooks. This is not good. Can someone tell me whether the Adobe team can read this suggestion?

Hi,
Thanks for the tip. It solved one problem, but the other problem remains. When you click a new page from table of contents, the zoom is lost. This is a bug I believe.

CS4 NOT capable of sharp displays at all zoom levels

I must have been asleep, until now, and missed the significance and importance of what follows.
In post #11 here:
http://forums.adobe.com/thread/375478?tstart=30
on 19 March 2009 Chris Cox (Adobe Photoshop Engineer - his title on the old forums) said this, in a discussion regarding sharpness in CS4:
"You can't have perfectly sharp images at all zoom levels.". Unfortunately, my experience with CS4 since its release late last year has repeatedly confirmed the correctness of this statement.
What makes this statement so disturbing is that it contradicts an overwhelming amount of the pre- and post-release promotional advertising of CS4 by Adobe, to the effect that the OpenGL features of CS4 enable it to display sharp images at all zoom levels and magnifications. What is surprising is that this assertion has been picked up and regurgitated in commentary by other, sometimes highly experienced, Ps users (some unconnected with, but also some directly connected with, Adobe). I relied upon these representations when making my decision to purchase the upgrade from CS3 to CS4. In fact, they were my principal reason for upgrading. Without them, I would not have upgraded. Set out in numbered paragraphs 1 to 6 below is a small selection only of this material.
1. Watch the video "Photoshop CS4: Buy or Die" by Deke McClelland (inducted into the Photoshop Hall of Fame, according to his bio) on the new features of CS4 in a pre-release commentary to be found here:
http://fyi.oreilly.com/2008/09/new-dekepod-deke-mcclelland-on.html
Notice what he says about zooming with Open GL: "every zoom level is a bicubically rendered thing of beauty". That, when viewed with the zooming demonstrated, can only be meant to convey that your image will be "sharp" at all zoom levels. I'm sure he believes it too - Deke is someone who is noted for his outspoken criticism of Photoshop when he believes it to be deserved. It would seem that he must not have experimented and tested to the extent that others posting in this forum have done so.
2. Here's another Adobe TV video from Deke McClelland:
http://tv.adobe.com/#vi+f1584v1021
In this video Deke discusses the "super smooth" and "very smooth" zooming of CS4 at all zoom levels achieved through the use of OpenGL. From the context of his comments about zooming to odd zoom levels like 33.33% and 52.37%, it is beyond doubt that Deke's use of the word "smooth" is intended to convey "sharp". At the conclusion of his discussion on this topic he says that, as a result of CS4's "smooth and accurate" as distinct from "choppy" (quoted words are his) rendering of images at odd zoom levels (example given in this instance was 46.67%), "I can actually soft proof sharpening as it will render for my output device".
3. In an article by Philip Andrews at photoshopsupport.com entitled 'What's New In Adobe Photoshop CS4 - Photoshop 11 - An overview of all the new features in Adobe Photoshop CS4',
see: http://www.photoshopsupport.com/photoshop-cs4/what-is-new-in-photoshop-cs4.html
under the heading 'GPU powered display', this text appears :
"Smooth Accurate Pan and Zoom functions – Unlike previous versions where certain magnification values produced less than optimal previews on screen, CS4 always presents your image crisply and accurately. Yes, this is irrespective of zoom and rotation settings and available right up to pixel level (3200%)." Now, it would be a brave soul indeed who might try to argue that "crisply and accurately" means anything other than "sharply", and certainly, not even by the wildest stretch of the imagination, could it be taken to mean "slightly blurry but smooth" - to use the further words of Chris Cox also contained in his post #11 mentioned in the initial link at the beginning of this post.
4. PhotoshopCAFE has several videos on the new features of CS4. One by Chris Smith here:
http://www.photoshopcafe.com/cs4/vid/CS4Video.htm
is entitled 'GPU Viewing Options". In it, Chris says, whilst demonstrating zooming an image of a guitar: "as I zoom out or as I zoom in, notice that it looks sharp at any resolution. It used to be in Photoshop we had to be at 25, 50 , 75 (he's wrong about 75) % to get the nice sharp preview but now it shows in every magnification".
5. Here's another statement about the sharpness of CS4 at odd zoom levels like 33.33%, but inferentially at all zoom levels. It occurs in an Adobe TV video (under the heading 'GPU Accererated Features', starting at 2 min 30 secs into the video) and is made by no less than Bryan O'Neil Hughes, Product Manager on the Photoshop team, found here:
http://tv.adobe.com/#vi+f1556v1686
After demonstrating zooming in and out of a bunch of documents on a desk, commenting about the type in the documents which is readily visible, he says : "everything is nice and clean and sharp".
6. Finally, consider the Ps CS4 pdf Help file itself (both the original released with 11.0 and the revised edition dated 30 March 2009 following upon the release of the 11.0.1 update). Under the heading 'Smoother panning and zooming' on page 5, it has this to say: "Gracefully navigate to any area of an image with smoother panning and zooming. Maintain clarity as you zoom to invididual pixels, and easily edit at the highest magnification with the new Pixel Grid." The use of the word "clarity" can only mean "sharpness" in this context. Additionally, the link towards the top of page 28 of the Help file (topic of Rotate View Tool) takes you to yet another video by Deke McClelland. Remember, this is Adobe itself telling you to watch this video. 5 minutes and 40 seconds into the video he says: "Every single zoom level is fluid and smooth, meaning that Photoshop displays all pixels properly in all views which ensures more accurate still, video and 3D images as well as better painting, text and shapes.". Not much doubt that he is here talking about sharpness.
So, as you may have concluded, I'm pretty upset about this situation. I have participated in another forum (which raised the lack of sharp rendering by CS4 on several occasions) trying to work with Adobe to overcome what I initially thought may have been only a problem with my aging (but nevertheless, just-complying) system or outdated drivers. But that exercise did not result in any sharpness issue fix, nor was one incorporated in the 11.0.1 update to CS4. And in this forum, I now read that quite a few, perhaps even many, others, with systems whose specifications not only match but well and truly exceed the minimum system requirements for OpenGL compliance with CS4, also continue to experience sharpness problems. It's no surprise, of course, given the admission we now have from Chris Cox. It seems that CS4 is incapable of producing the sharp displays at all zoom levels it was alleged to achieve. Furthermore, it is now abundently clear that, with respect to the issue of sharpness, it is irrelevant whether or not your system meets the advertised minimum OpenGL specifications required for CS4, because the OpenGl features of CS4 simply cannot produce the goods. What makes this state of affairs even more galling is that, unlike CS3 and earlier releases of Photoshop, CS4 with OpenGL activated does not even always produce sharp displays at 12.5, 25, and 50% magnifications (as one example only, see posts #4 and #13 in the initial link at the beginning of this post). It is no answer to say, and it is ridiculous to suggest (as some have done in this forum), that one should turn off OpenGL if one wishes to emulate the sharp display of images formerly available.

Thanks, Andrew, for bringing this up. I have seen comments and questions in different forums from several CS4 users who have had doubts about the new OpenGL display functionality and how it affects apparent sharpness at different zoom levels. I think part of the interest/doubt has been created by the over-the-top hype that has been associated with the feature as you documented very well.
I have been curious about it myself and honestly I didn't notice it at first but then as I read people's comments I looked a little closer and there is indeed a difference at different zoom levels. After studying the situation a bit, here are some preliminary conclusions (and I look forward to comments and corrections):
The "old", non-OpenGL way of display was using nearest-neighbor interpolation.
I am using observation to come to this conclusion, using comparison of images down-sampled with nearest-neighbor and comparing them to what I see in PS with OpenGL turned off. They look similar, if not the same.
The "new", OpenGL way of display is using bilinear interpolation.
I am using observation as well as some inference: The PS OpenGL preferences have an option to "force" bilinear interpolation because some graphics cards need to be told to force the use of shaders to perform the required interpolation. This infers that the interpolation is bilinear.
Nothing is truly "accurate" at less than 100%, regardless of the interpolation used.
Thomas Knoll, Jeff Schewe, and others have been telling us that for a long time, particularly as a reason for not showing sharpening at less than 100% in ACR (We still want it though ). It is just the nature of the beast of re-sampling an image from discrete pixels to discrete pixels.
The "rule of thumb" commonly used for the "old", non-OpenGL display method to use 25%, 50%, etc. for "accurate" display was not really accurate.
Those zoom percentages just turned out to be less bad than some of the other percentages and provided a way to achieve a sort of standard for comparing things. Example: "If my output sharpening looks like "this" at 50% then it will look close to "that" in the actual print.
The "new", OpenGL interpolation is certainly different and arguably better than the old interpolation method.
This is mainly because the more sophisticated interpolation prevents drop-outs that occurred from the old nearest-neighbor approach (see my grid samples below). With nearest-neighbor, certain details that fall into "bad" areas of the interpolated image will be eliminated. With bilinear, those details will still be visible but with less sharpness than other details. Accuracy with both the nearest-neighbor and bilinear interpolations will vary with zoom percentage and where the detail falls within the image.
Since the OpenGL interpolation is different, users may need to develop new "rules of thumb" for zoom percentages they prefer when making certain judgements about an image (sharpening, for example).
Note that anything below 100% is still not "accurate", just as it was not "accurate" before.
As Andrew pointed out, the hype around the new OpenGL bilinear interpolation went a little overboard in a few cases and has probably led to some incorrect expectations from users.
The reason that some users seem to notice the sharpness differences with different zooms using OpenGL and some do not (or are not bothered by it) I believe is related to the different ways that users are accustomed to using Photoshop and the resolution/size of their monitors.
Those people who regularly work with images with fine details (pine tree needles, for example) and/or fine/extreme levels of sharpening are going to see the differences more than people who don't. To some extent, I see this similar to people who battle with moire: they are going to have this problem more frequently if they regularly shoot screen doors and people in fine-lined shirts. Resolution of the monitor used may also be a factor. The size of the monitor in itself is not a factor directly but it may influence how the user uses the zoom and that may in turn have an impact on whether they notice the difference in sharpness or not. CRT vs LCD may also play a role in noticeability.
The notion that the new OpenGL/bilinear interpolation is sharp except at integer zoom percentages is incorrect.
I mention this because I have seen at last one thread implying this and an Adobe employee participated who seemed to back it up. I do not believe this is correct. There are some integer zoom percentages that will appear less sharp than others. It doesn't have anything to do with integers - it has to do with the interaction of the interpolation, the size of the detail, and how that detail falls into the new, interpolated pixel grid.
Overall conclusion:
The bilinear interpolation used in the new OpenGL display is better than the old, non-OpenGL nearest-neighbor method but it is not perfect. I suspect actually, that there is no "perfect" way of "accurately" producing discrete pixels at less than 100%. It is just a matter of using more sophisticated interpolation techniques as computer processing power allows and adapting higher-resolution displays as that technology allows. When I think about it, that appears to be just what Adobe is doing.
Some sample comparisons:
I am attaching some sample comparisons of nearest-neighbor and bilinear interpolation. One is of a simple grid made up of 1 pixel wide lines. The other is of an image of a squirrel. You might find them interesting. In particular, check out the following:
Make sure you are viewing the Jpegs at 100%, otherwise you are applying interpolation onto interpolation.
Notice how in the grid, a 50% down-sample using nearest-neighbor produces no grid at all!
Notice how the 66.67% drops out some lines altogether in the nearest-neighbor version and these same lines appear less sharp than others in the bilinear version.
Notice how nearest-neighbor favors sharp edges. It isn't accurate but it's sharp.
On the squirrel image, note how the image is generally more consistent between zooms for the bilinear versions. There are differences in sharpness though at different zoom percentages for bilinear, though. I just didn't include enough samples to show that clearly here. You can see this yourself by comparing results of zooms a few percentages apart.
Well, I hope that was somewhat helpful. Comments and corrections are welcomed.

REQ: Add 'Fit-width' or 'Fit-visible' view mode, in which the zoom level is automatically set based on the width of the _current_ page.

Currently, the default zoom level when viewing a page of a PDF file is automatically calculated based on the width of the "widest" page of the document. This means that, if the document contains one page that is wider than the others or is in landscape orientation, then the default zoom, when viewing all the other narrower pages, is set in a way so that the page does not use the full width of the screen. This results in very poor experience, because the zoom level and the visible area of the page have to be constantly adjusted for each page. The latest update (at the time of writing) has added some extra view modes, but not the much needed 'Fit width' or 'Fit visible'.
Personally, I can find no reason valid enough to justify the lack of such a view mode. Automatically setting the zoom level based on the width of the current page so as to take advantage of the full width of the screen should be a must have feature for mobile devices, if not the default behavior. The current default behavior regarding the zoom level is pretty much useless, even on 8"/10" screens. There should be a view mode in which the full width of the screen is always used to display the document.
Examples of documents for which the Adobe Reader for Android provides a poor reading experience are:
documents which contain some of their pages in landscape orientation.
publications which, apart from the main content, also contain the full front and back cover in a single page (usually first page which is much wider than the content pages) or any other extra pages like cards or application forms (that are meant to be printed) which usually use an A4/Letter page size etc.
documents which have been cropped by external utilities or scripts so as to eliminate unneeded white margins (in some cases not all pages have the same width).
Please consider fixing the default behavior in future releases of the Reader for Android or add a 'Fit width' or 'Fit visible' view mode.
Thank you in advance.
Message was edited by: George Notaras
Improved descriptions of example documents.

To add to this, if you prefer you can separate your JavaScript from your JSF pages.
Add a folder (I named mine 'js') to your application's ViewController project's public_html folder.
Via JDeveloper, create a new JavaScript file inside your newly created folder and place your JavaScript functions inside it.
You can then 'load' the .js file using the method Shantala described, with the addition of an added 'source' property to the af:reference tag.
(This can also be a URI reference to a JavaScript file hosted on a web server)
<f:facet name="metaContainer">
<af:resource source="/js/myJsFile.js" type="javascript"/>
</f:facet>The benefits of this 'split' are cleaner JSF page source and also code-highlighting and formatting within the .js file making finding and fixing bugs in your JavaScript much easier.
It appears however, that when using <af:resource> to load scripts, once the page has been submitted even once, the JavaScript is no longer available to the page. Which isn't very useful.
A solution is to use <trh:script>.
Add xmlns:trh="http://myfaces.apache.org/trinidad/html" to your <jsp:root> tag and install the library.
then in place of the above code use:
<f:facet name="metaContainer">
<trh:script id="script1" source="/js/myJsFile.js"/>
</f:facet>Now after a page submit the JavaScript still functions.
Edited by: Matthew Carrigy on 12/08/2009 10:39

Can you set PDF zoom level when exporting from ID?

I do many documents for proof and regardless of how the end user is going to view them, I like them to open as a full page ("Fit Page" zoom level) - I want the viewer to get the overall impact of the layout before they see just the top half or upper corner.
Right now, I export from ID and have to manually set the zoom level in Properties from within Acrobat Pro. Is there ANY way to set a default export zoom level to save this step, which I have to do many times on most days?

Only if you export using File > Export > Adobe PDF (Interactive). Not if you're using File > Export > Adobe PDF (Print),

Make table of contents links keep current zoom level, not zoom out to full page

When Indesign creates tables of contents, they automatically link to the paragraphs the links point to, so that in an interactive PDF, clicks and prods take the user to that page. Great.
What's not so great is, that the hyperlinks / cross-references / jump-links / whatever that are created behind the scenes within the table of contents appear to:
...be automatically set to reset the zoom to full page width
...not be editable in any way
Normal cross references retain the zoom level that the user has chosen, and normal hyperlinks that point to a page in the document have a range of settings about what zoom level change (if any) should be imposed on the user, which can be set to 'inherit zoom'.
How do I set up a table of contents that doesn't annoy users by resetting their chosen zoom level to an artitrary default when they use the interactive table of contents?
I'm really hoping I don't have to ditch Indesign's table of contents feature and create every cross reference manually.

(editted) So it turns out that you can 'expand' a table of contents by copying and pasting it - this fills the hyperlinks panel with links that can be editted (like above) but breaks the auto-update - they're no longer a TOC, they're just a text frame full of links. (I had got different copies mixed up when I thought the frame holding the editable links was also auto-updating)
The greying out of the links was a red herring, just something to do with the fact they were on a master page.
It does mean that one possible TOC workflow is:
Create a TOC on the pasteboard somewhere.
Before finalising the document, update this TOC and alt-drag the 'live' TOC creating an editable 'dead' copy in an appropriate place in the document
Edit the link properties of the links in the 'dead' copy (don't forget that you can select multiple hyperlinks at once by holding down shift, and edit things like the Zoom Setting all at once with Hyperlink Options in the Hyperlinks flyout menu. )
Then, if you make other changes to the document later on, delete the dead copy, update and re-copy the live original, and re-do the changes to the new copy
This isn't a bad method - it just adds about a minute's work each time you export a PDF (delete, update TOC, alt-drag, shift-select the new batch of .XXXX links at the bottom of the Hyperlinks panel, > Hyperlink Options, Zoom Setting > Inherit Zoom, done).
Alternatively, you could manually build a TOC using cross-references if you want links to the exact position on the page, not just the top of the appropriate page.

Screen permanently zoomed in- Magic Prefs??? After configuring "two finger zoom in" in Magic Prefs, screen is permanent;y zoomed in how do I overide Magic Prefs and switch off zoom?

Hi. I went into Magic Preferences to configure a "2 finger pinch out" as zoom in and a "2 finger pinch in" as zoom out of screen. In short, the zoom in worked and the zoom out didn't. Now my IMac screen is permanently zoomed in and I cant tell where abouts I am on the screen to switch off or overide the stupid magic prefs of my magic mouse. I have tried holding CONTROL, scroll down arrow but didn't work.
Thanks in advance. Dennis

Try holding down Control while using the single-finger scroll gesture on the Magic Mouse. In Snow Leopard you would use the scroll-down gesture (drag finger toward you), but if you are use Lion the gesture may be reversed.
Another possibility - go to System Preferences > Universal Access, click the Seeing choice. See if Zoom got activated accidentally. If it is "on", change it to '"off".
Note that there is a keyboard command (shortcut) available to toggle that Zoom: Command-Option-8
You can disable that shortcut in System Preferences > Keyboard, Keyboard Shortcuts section - click the Universal Access item in the left-hand pane, then uncheck the "turn zoom on or off" item in the right-hand pane.
Note - the descriptions I gave for what is where applies to Snow Leopard. If you are using Lion, there should be simialr settings although their specific locations may be slightly different.

Safari on rMBP has 200% zoom level by default when viewing standalone images.

I have a MacBook Air 13" Mid 2010 and recently purchased a MacBook Pro with Retina Display 15" Mid 2012. I have updated Safari to 6.0 on both machines, but here comes the problem when I use Safari to view a standalone image on my rMBP.
Normally when I view a standalone image on Safari, the zoom level is 100% which means I see the actual pixeles of the image. Once you open an image in a new tab or a new window, if the dimensions of the image is bigger than the window, let's say 5000x4000, the dimensions of the image will be adjusted to fit within the window. And then the cursor becomes a tiny circle with the "+" sign inside (sorry for my poor description, I hope you can get it) which is the zoom icon, by clicking the image you zoom to the actual pixels of the image which shows 100% of the image.
However this works on my MBA but it doesn't on my rMBP as the zoom level is 200% by default. The following web pages are the ones where I found to have the same problem and they have better explanations:
http://notes.jayrobinson.org/post/25599469833/the-images-above-show-safari-5-2-w ith-page-zoom-on
https://twitter.com/jayrobinson/status/214443964516937729
Sorry for the long post, but I just wonder if there is a way to fix the problem or if Apple can do it?

I've seen this reported before -- sometimes PSE needs to have the zoom set to even multiples of 25%. You can try searching Adobe's site to see if anyone has found a solution.
Ken

Any way to put your own zoom level in the zoom dropdown?

It turns out that on my 15.6" laptop screen a 65% zoom level is about perfect for fitting my spread in the display so that I can actually read the text in the text frames. (Double-clicking the Zoom tool puts me at a 75% zoom level but with text frames going outside my screen viewing area).
Pressing Control-Alt-0 puts me at 53.3% but with text slightly too small to read. Being stubborn, I want 65%, because then I can read all my text and fit the whole spread in the window minus the white blank area between the pink (magenta?) margins and the page trim (black border) which I don't need to see.
I know about the script method - I've already made my own keyboard shortcut for a 60% zoom level using a custom zoom60.jsx script file with a Control-Shift-1 keyboard shortcut.
Is there any way to add that 65% zoom level to the Zoom dropdown menu on the Application Bar (top of window)?
Note: You can't set a default Zoom level with no documents open because the Zoom control (dropdown at top) is greyed out - not accessible.

I found the ultimate solution to this - buy a new (business model) laptop with a better video card and screen. My top ("recommended") resolution is now 1600 x 900. The old one had a top resolution of 1366 x 768.
Pressing Control-Alt-0 to Fit Spread in Window on the old laptop gives me a 53% zoom level with fuzzy text that borders on unreadable. Pressing Control-Alt-0 on the new laptop gives me a 65% zoom level with text readable.
But, what I want is a command called: Fit Spread in Window But With A Smidgeon of White Showing Beyond The Margins. That turns out to be a 75% zoom level for me (which exists as a preset in the Zoom dropdown on the Application Bar at top of the interface), but I'll still need to do a script and map it to something like Control-Shift-1 because 75% does not result from any of the choices under the View menu. (Using Control-minus(-) and Control-plus(+) will get me to the 75% though). And, I want to get to that 75% without using the mouse.
Without getting too technical, I think working on a program like InDesign on a consumer model laptop (Acer Aspire 5535) with one of those horrible shiny screens is basically bad for your eyes. I'm now on a Lenovo Thinkpad W530 with beautiful matte screen (no glare) and text with very sharp edges.
I guess there are other solutions - like mapping Control-Alt-0 to a 75% zoom using a script to replace my current 65% zoom level.

Permanent zoom level within Reading pane

Similar Messages

Maybe you are looking for