Save Zoom Level Preference After Exiting Spotify

It would be great if the desktop Spotify app saves the zoom level setting so that we won't have to zoom in/out back to our desired level each time we open Spotify

OK guys, I went to Help > About Spotify to download the newest update. After I click dlownload it now it just says "Downloading a new version of Spotify...." and never changes. Was sitting like that for hours before I cancelled it. I really want the update for the playlist filtering! What do I need to do here?

Similar Messages

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.

Zoom error after exiting iPhoto presentation

The screen zoom stop working after I exit an iPhoto Slides Presentation. I need to logout and login again in my Mac to get zoom work. I checked tha configurations on Universal Access, under System Preferences, and the zoom appears as Active even when the zoom doesn't work, after the presentation.
Is it a bug of Mac or iPhoto?
I use Mac OS Lion 10.7.2 and iPhoto '11 (9.2.1 - 628), on MacBook Pro.

Adittional info: if I close the slideshow, desactive and reactive the zoom, in Universal Access, the zoom with the keyboar (Command+Option+= and Command+Option+-) works, but the zoom with the mouse (scrolling) don't.

How to find the ME29N 'USER EXIT' when our save the release PO after.

How to find the ME29N 'USER EXIT' when our save the release PO after.
which user exit will be used?
thanks.
alex.

Hi,
process :
    go to tranx code :   ME29N ,
       System---->Status , here copy the program name (SAPLMEGUI),
     go to abap editor and specify the program name SAPLMEGUI and find the package "ME".
     tranx code : CMOD , Utilites--->Sap Enanchement,
                                     specify the package name : ME
                                      and execute, displays a list of exits ,
                             and find out our suitable exit based on requirement.
check these :   EXIT_SAPMM06E_021
reg
Siva

Regarding Firefox 4 does not ask to save tabs and windows on exit even after trying all suggestions

After installing Firefox 4, Firefox would no longer ask to save tabs and windows on exit. Even after trying all suggestions to resolve the problem, the problem continued. Under the corrupted files suggestion to rename two files, that also did not help. The original file names would be recreated automatically, so both file name versions would exist in that folder. NOTHING resolves the problem.
Unfortunately, since that is a very desirable feature I, like other people who do not like Firefox 4, have gone back to an earlier version of Firefox.

You can set the warn prefs on the about:config page to true via the right-click context menu or toggle with a double left-click.
* browser.showQuitWarning, see http://blog.zpao.com/post/3174360617/about-that-quit-dialog
* browser.tabs.warnOnClose, see http://kb.mozillazine.org/About%3Aconfig_entries
* browser.warnOnQuit , see http://kb.mozillazine.org/browser.warnOnQuit
* browser.warnOnRestart , see http://kb.mozillazine.org/browser.warnOnRestart
* browser.startup.page , seehttp://kb.mozillazine.org/browser.startup.page (1 or 2)
To open the about:config page, type about:config in the location (address) bar and press the "Enter" key, just like you type the url of a website to open a website. 
If you see a warning then you can confirm that you want to access that page. 
You can use "Firefox > History > Restore Previous Session" to get back the previous session. 
There is also a "Restore Previous Session" button on the default about:home Home page.
Another possibility is to use:
*Tools > Options > General > Startup: "When Firefox Starts": "Show my windows and tabs from last time"

Setting zoom level

I am using version Adobe Reader X version 10.1 on Windows.
I set the zoom level in Preferences | Page Display | Zoom to 100%. I save it. I close the pdf I am viewing. I reopen the PDF. The PDF is shown at zoom level 72.3 %.
Why is this so hard to get right for Adobe Reader ? This problem has persisted for every version of Adobe Reader I have used since the product was created. This is not rocket science, Adobe developers. Do you think you can get this correct before the end of the earth some X billions of years down the line.
Eddie

Using Acrobat a content author can configure the Initial View of a PDF in the PDF's Document Properties.
Any such configuration determines the initial view of the PDF when opened by Adobe Reader or Acrobat.
Been that way back to Acrobat 4.x.
This permits the content author to establish a desired initial view for their product or to establish a common initial view for PDFs deployed by a business.
If the value "Default" is selected or an item is not ticked then the Adobe Reader / Acrobat Preferences settings come into play.
Be well...

How can I save zoom setting for a DOCUMENT so it opens at that setting?

I find an optimal zoom setting for a document I'd like to use (say 42%) and want the document to open at that setting. I save the document with File>Save Copy. However when I open the document, it opens at the DEFAULT zoom setting set in the Preferences for program. If I change the zoom level here to what I desire for that document, obviously all documents will open at that default setting.
How can I save my desired zoom level for a document, which will most likely be different for EACH document, and have the saved document open at that setting?
This seems like a trivial exercise / feature that should be easy to implement BOTH by the programmers of the software and the user setting the zoom level.
Also, I want to suppress the bookmarks sidebar. I save without the bookmarks but the documents opens with the side bar. Can't THIS be set for each document?
Why is it so difficult to tailor the viewing of a document to exactly what the viewer wants?

OK. Sorry for the mistake in posting the question here.
Again it seems like it should be trivial to save a document in the Reader with a viewer's desired zoom setting. I find this very helpful as I like to use a zoom setting that when scrolling down the document only one full page of the document is viewed (like turning the pages of a book). Without this feature, partial pages are displayed when scrolling unless one experiments to find the correct zoom setting (often it is 60%). One must do this every time one opens the same document, unless one remembers the zoom setting.
Oh well ....

Nosquint's Global zoom level setting can not be saved

I change the Global zoom level setting 140 from 150, and it works a 140. after I quit FF and back again, the Global zoom level is changed back to 150 again, it seems that can not be saved. it is working under V21
I am using ff 24.0 now
any solution?

You can check for problems with preferences. 
Rename or delete the prefs.js file and possible numbered prefs-##.js and user.js files to reset all prefs to the default value.
*http://kb.mozillazine.org/Preferences_not_saved
*http://kb.mozillazine.org/Resetting_preferences
You can rename the content-prefs.sqlite file to content-prefs.sqlite.old (or delete the file) in the Firefox profile folder to reset the page zoom for all websites.

InDesign Zoom Level

I'm having a problem on zoom level. Whenever I create a new document, my zoom level always too high. It's always showing at 700%, making my insertion point large whenever I create an text frame.

This looks familiar, did you ask this question a day or two ago? By default, all new documents are created at "fit page in window" size. There is no way I know of, short of scripting an action to change it immediately after opening, to change this. Have you tried replacing your preferences?

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 I lock in a zoom level (e.g. Page View) so it won't change?

I'm wondering if there is a way to prevent Adobe Reader from changing my zoom level. I prefer to read with the zoom level set to Fit Page. Every time I click on a bookmark to jump to another page in the document, the zoom level changes to Fit Width (I think). This is extremely annoying because I have to keep changing the view back to Fit Page. In preferences I have put the default zoom to Fit Page, but that only determines how it comes up initially. When I click on a bookmark it changes again.
I don't understand why the zoom changes when you click a bookmark at all. Why would I want the zoom to change on me?
FYI, I'm using Reader XI (11.0.08).
Thanks for any help/suggestions.

Thanks CtDave. I don't have anything besides the free reader, so I did some further research on the web and found a solution that is pretty "brute force", but is an option for others that only have the free reader. Here is a link to the full description:
http://superuser.com/questions/306803/zooming-size-of-pdf-files-and-bookmarks
Here is the basics: You can use a text editor and edit the PDF file. Once in the text editor you can search for /FitH or /Fit (there surely are other codes, but those are the only ones I know of). These are codes that tell Acrobat what kind of zoom level to apply to the destination of a jump. So the bookmarks should all have these. Simply do a search and replace with /XYZ. The /XYZ code tells Acrobat to leave the zoom level as it already is.
It might sound a bit weird, but I tried it on multiple files I was having trouble with and it worked great. Of course, my suggestion would be to make backup copy of the file before doing this in case something goes wrong.
Thanks.

Can I keep firefox at a 125% zoom level? I use my HDTV as a monitor and would like the view to be larger without having to hit "ctrl +" on each web page.

I would like firefox to default to a 125% zoom level. Is ther a way I can do this through firefox or through my desktop?

The following Add-on will allow you to set whatever default %-age works best for you. After install, go to Add-ons > Extensions > Default FullZoom Level > Options, in the Options window, "Default FullZoom Level (percent)". That will set ALL pages at your choice.
*'''''Default FullZoom Level''''': https://addons.mozilla.org/en-US/firefox/addon/default-fullzoom-level/
*Support for '''''Default FullZoom Level''''': http://forums.mozillazine.org/viewtopic.php?f=48&t=659681&start=75
Also look at NoSquint
*'''''NoSquint''''': https://addons.mozilla.org/en-US/firefox/addon/nosquint/
*More info on NoSquint: http://urandom.ca/nosquint/
'''If this reply solves your problem, please click "Solved It" next to this reply when signed-in to the forum.'''

How to keep the Zoom level in Safari 7?

There is only one big win that's making me stick to Chrome over Safari: The zoom.
In Chrome when you zoom in a page (With Cmd +) the zoom level is stored in the cookies, or the history, or somwhere, and it stays the same level when you open again that page in another tab or if you close and open again Chrome. This simple feature makes it tremendously comfortable to navigate in big and wide screens.
This feature by itself is going to keep me using Chrome instead of Safari with all the new fancy and cool stuff they added in the new Safari 7. And yes, there is a "Trick" by using a .css style sheet customed to make a default zoom in all pages, but it's not good enough because some pages need different level of zoom.
So please, someone, make Apple correct this issue. It should't be complicated, it's as simple as that Safari remembers the latest zoom level you left in a web.
Because I believe that if people are leaving Safari behind is because it lacks this simple tools that make life much easier. And I believe it's in Apples philosphy to make technology to help people, isn't it?

It never worked the way Chrome works in Safari 6 either, but at least Safari 6 remembered the zoom level you'd set in a particular tab. With Safari 7 Apple has made the situation even worse. Now after setting the zoom level you want, it's forgotten when you click on a bookmark, and the page reverts to actual size. It really is infuriating having to zoom in all the time, and the CSS trick and the various zoom extensions don't work properly. Safari is all but unusable for me because of this issue. I've complained to Apple many times about it in the past, but now I've given up believing it'll ever change. It seems that Chrome will forever conquer Safari thanks to an easy-to-fix issue Apple refuses to fix.

Zoom level when opening a pdf in Preview from a Finder "find" window

I do a Finder search, and the search window shows a bunch of pdf files. If I double click on one, it opens in Preview with the Finder search term highlighted in the pdf text-very nice. But the zoom level of the pdf is very high, like 300%. So I always need to zoom back out to 100% to see the context of the found term. Is there a way to change this default behavior?
Another point is that once I open one of the pdf's, it vanishes from the Finder window. Although this might make sense in some ways, because, after all, I've already had a look at the file, it's often not the behavior I want. In particular, it's hard to know what the next pdf is that I was going to open, when the one I just looked at is no longer in the list. I should also point out that not all pdf's vanish in this way, but most do. I can't see any pattern.

Hi,
You mentioned that "JavaScript in the PDF can hide toolbar buttons."
According to the Javascript docs for Acrobat 7 the App.HideToolbarButton function only runs at AppInit. Which means that I would have to have the javascript in a file. How can I do that from within the document? Is there another way to to do set this from our web application?
Rob

Mac Sleep Timer (through 'Energy Saver' in System Preferences) won't work

Hello,
I have a MacBook (13-inch, Mid 2009) running Mac OS X Snow Leopard 10.6.3,
and it has been installed with the latest software updates possible.
(The latest update is the 'Security Update 2010-003')
Previously I was using Mac OS X Leopard 10.5 on my MacBook,
and I can vaguely remember the timed computer sleep through Energy Saver would work.
That is, when the counter's time matches the amount of time I specified (e.g. 10 minutes), the computer enters sleep mode and displays a pulsing power light.
After upgrading to Snow Leopard I can barely remember the scheduled computer sleep will work as I don't really notice how it sleeps / I will shut down my MacBook before I go to bed.
==========
However, last night I was really tired and slept in front of my MacBook unconsciously.
When I woke up, I found that my MacBook didn't display a pulsing power light but a continuously-growing power light.
I tapped the trackpad and the display turned on, so I knew that my MacBook didn't go to sleep a whole night.
*What that means is that the Sleep Timer (through 'Energy Saver' in System Preferences) won't work.*
But the timed display sleep DOES work.
==========
After spending a whole day Googling,
I found that there are plenty of people suffering the same problem as me, although their Macs and OSs vary.
I also found an official support page from Apple concerning the related issue:
Mac OS X: Why your Mac might not sleep or stay in sleep mode
http://support.apple.com/kb/HT1776
I tried the following methods but still can't resolve the problem:
_- boot my MacBook in safe mode_
_- use the 'Disk Utility' to repair Disk Permissions through booting my MacBook from the Mac OS X Snow Leopard Installation DVD_
_- reset NVRAM (Intel-based) (as PRAM is used by PowerPC-based Macs)_
_- reset SMC (System Management Controller)_
NONE of the above-mentioned methods can resolve the problem.
Althought I am sure that the Spotlight isn't indexing the hard drive, and I just start my computer and do nothing and wait for the scheduled computer sleep, the scheduled computer sleep just won't work.
In the other Mac forum, I saw someone suggest installing an application called PleaseSleep:
http://www.dragonone.com/products/macosx/pleasesleep/
It works.
But I really want to find out what caused this problem as this is a function shipped with Mac which is expected to work normally.
What's more, Apple is claiming to be a green Apple, right?
==========
Here's the log taken from 'Console':
- Sleep by closing the lid of my MacBook:
Apr 18 13:21:05 Michael-Leungs-MacBook loginwindow[25]: loginwindow SleepWakeCallback WILL sleep
Apr 18 13:21:05 Michael-Leungs-MacBook PleaseSleep[288]: Sleep notification received from the system
Apr 18 13:21:07 Michael-Leungs-MacBook configd[37]: network configuration changed.
Apr 18 13:23:21 Michael-Leungs-MacBook loginwindow[25]: loginwindow SleepWakeCallback will power on, Currenttime:4/18/2010 1:23:21.028 PM - Waketime:4/18/2010 1:23:19.410 PM = Deltatime:1.618421972
Apr 18 13:23:21 Michael-Leungs-MacBook loginwindow[25]: handleUnlockResult, Currenttime:4/18/2010 1:23:21.579 PM - Waketime:4/18/2010 1:23:19.410 PM = Deltatime:2.169138968
Apr 18 13:23:23 Michael-Leungs-MacBook configd[37]: Sleep: Success - AC 98 - Clamshell Sleep
Apr 18 13:23:23 Michael-Leungs-MacBook configd[37]: Wake: Success - AC 98 - EC LID0
Apr 18 13:23:23 Michael-Leungs-MacBook configd[37]: Hibernate Statistics
Apr 18 13:23:23 Michael-Leungs-MacBook PleaseSleep[288]: Wake notification received from the system
- Sleep by manually clicking the Apple logo in the upper left corner of the screen -> 'Sleep':
Apr 18 13:31:46 Michael-Leungs-MacBook loginwindow[25]: loginwindow SleepWakeCallback WILL sleep
Apr 18 13:31:46 Michael-Leungs-MacBook PleaseSleep[288]: Sleep notification received from the system
Apr 18 13:31:49 Michael-Leungs-MacBook configd[37]: network configuration changed.
Apr 18 13:32:04 Michael-Leungs-MacBook loginwindow[25]: loginwindow SleepWakeCallback will power on, Currenttime:4/18/2010 1:32:04.033 PM - Waketime:4/18/2010 1:32:02.720 PM = Deltatime:1.313067079
Apr 18 13:32:04 Michael-Leungs-MacBook loginwindow[25]: handleUnlockResult, Currenttime:4/18/2010 1:32:04.589 PM - Waketime:4/18/2010 1:32:02.720 PM = Deltatime:1.869303048
Apr 18 13:32:06 Michael-Leungs-MacBook configd[37]: Sleep: Success - AC 98 - Software Sleep
Apr 18 13:32:06 Michael-Leungs-MacBook configd[37]: Wake: Success - AC 98 - OHC1
Apr 18 13:32:06 Michael-Leungs-MacBook configd[37]: Hibernate Statistics
Apr 18 13:32:06 Michael-Leungs-MacBook PleaseSleep[288]: Wake notification received from the system
- Sleep by manually pressing control + eject, and the press 'Sleep':
Apr 18 13:34:17 Michael-Leungs-MacBook loginwindow[25]: loginwindow SleepWakeCallback WILL sleep
Apr 18 13:34:17 Michael-Leungs-MacBook PleaseSleep[288]: Sleep notification received from the system
Apr 18 13:34:46 Michael-Leungs-MacBook loginwindow[25]: loginwindow SleepWakeCallback will power on, Currenttime:4/18/2010 1:34:46.080 PM - Waketime:4/18/2010 1:34:44.720 PM = Deltatime:1.360466003
Apr 18 13:34:46 Michael-Leungs-MacBook loginwindow[25]: handleUnlockResult, Currenttime:4/18/2010 1:34:46.564 PM - Waketime:4/18/2010 1:34:44.720 PM = Deltatime:1.844347000
Apr 18 13:34:46 Michael-Leungs-MacBook configd[37]: PMConnection AirPort configd plug-in com.apple.powermanagement.applicationresponse.slowresponse 566 ms
Apr 18 13:34:46 Michael-Leungs-MacBook configd[37]: bootpsessiontransmit: bpf_write(en0) failed: Network is down (50)
Apr 18 13:34:46 Michael-Leungs-MacBook configd[37]: DHCP en0: INIT transmit failed
Apr 18 13:34:46 Michael-Leungs-MacBook configd[37]: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 567 ms
Apr 18 13:34:46 Michael-Leungs-MacBook configd[37]: network configuration changed.
Apr 18 13:34:48 Michael-Leungs-MacBook configd[37]: Sleep: Success - AC 98 - Software Sleep
Apr 18 13:34:48 Michael-Leungs-MacBook configd[37]: Wake: Success - AC 98 - OHC1
Apr 18 13:34:48 Michael-Leungs-MacBook configd[37]: Hibernate Statistics
Apr 18 13:34:48 Michael-Leungs-MacBook PleaseSleep[288]: Wake notification received from the system
- Sleep by _turning on the application called 'PleaseSleep' based on the settings from 'Energy Saver'_:
Apr 18 13:37:22 Michael-Leungs-MacBook PleaseSleep[288]: Application is enabled
Apr 18 13:37:29 Michael-Leungs-MacBook System Preferences[1136]: * AGCAttach() failed
Apr 18 13:37:31 Michael-Leungs-MacBook [0x0-0x58058].com.apple.systempreferences[1136]: Couldn't find any matches.
Apr 18 13:38:23 Michael-Leungs-MacBook PleaseSleep[288]: Checking sleep conditions...
Apr 18 13:38:23 Michael-Leungs-MacBook PleaseSleep[288]: Going to sleep...
Apr 18 13:38:23 Michael-Leungs-MacBook loginwindow[25]: loginwindow SleepWakeCallback WILL sleep
Apr 18 13:38:23 Michael-Leungs-MacBook PleaseSleep[288]: Sleep notification received from the system
Apr 18 13:38:56 Michael-Leungs-MacBook loginwindow[25]: loginwindow SleepWakeCallback will power on, Currenttime:4/18/2010 1:38:56.042 PM - Waketime:4/18/2010 1:38:54.720 PM = Deltatime:1.321902931
Apr 18 13:38:56 Michael-Leungs-MacBook loginwindow[25]: handleUnlockResult, Currenttime:4/18/2010 1:38:56.571 PM - Waketime:4/18/2010 1:38:54.720 PM = Deltatime:1.850627959
Apr 18 13:38:56 Michael-Leungs-MacBook configd[37]: PMConnection AirPort configd plug-in com.apple.powermanagement.applicationresponse.slowresponse 707 ms
Apr 18 13:38:56 Michael-Leungs-MacBook configd[37]: bootpsessiontransmit: bpf_write(en0) failed: Network is down (50)
Apr 18 13:38:56 Michael-Leungs-MacBook configd[37]: DHCP en0: INIT transmit failed
Apr 18 13:38:56 Michael-Leungs-MacBook configd[37]: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 708 ms
Apr 18 13:38:56 Michael-Leungs-MacBook configd[37]: network configuration changed.
Apr 18 13:38:58 Michael-Leungs-MacBook configd[37]: Sleep: Success - AC 98 - Software Sleep
Apr 18 13:38:58 Michael-Leungs-MacBook configd[37]: Wake: Success - AC 98 - OHC1
Apr 18 13:38:58 Michael-Leungs-MacBook configd[37]: Hibernate Statistics
Apr 18 13:38:58 Michael-Leungs-MacBook PleaseSleep[288]: Wake notification received from the system
- If I disable 'PleaseSleep' and only depend on the non-working 'Energy Saver', nothing happens.
==========
Looking forward to your replies! Thanks in advance!

Found this discussion by googling "com.apple.systempreferencescouldn't find any matches"...
One month ago I bought a brand new Macbook Pro 13", and after a couple of weeks I realized it wasn't sleeping on its own when it should, per the system preferences. (I did sleep when I chose "Sleep" in the menus or closed it... It just wouldn't sleep on its own, while open.) What was extra frustrating was that it was intermittent... It would sleep on its own maybe 1/3 of the time, but other times it would NEVER go to sleep. I deleted PowerManagement.plist, reset the SMC, etc... No luck.
I took it to the "geniuses" at the Apple Store, and the guy took all of five minutes trying to diagnose the problem. When my MBP wouldn't sleep on its own, he promptly replaced it with a new one. That was nice, but I actually would have preferred that he diagnosed and fixed it. (I think the store was so swamped with people coming in for service that day that they were doing anything they could to close cases and get customers out of there ASAP.)
Now, sitting here with my 48-hour-old MBP, I still have the problem. The other one was so new that I had barely put anything on it yet. The only applications I had put on it were MS Office for Mac 2011, Firefox, Chrome, and Adobe Flash Player. I've put Office and Flash Player on this one, but not yet Firefox or Chrome. That's it. No other customization or fancy business.
I looked into the Console just now, and I see the "Couldn'tfind any matches" entry popping up again and again. The last three seemed to pop upright around the time when my MBP should have gone to sleep on its own, but not down to the second, so it's hard to definitively point at that and say it's it for sure.
They need to fix this!!

Save Zoom Level Preference After Exiting Spotify

Similar Messages

Maybe you are looking for