Google/Bing Zoom Level

I have successfully configured Google/Bing map tile layer with our own map tile layers. I want to add more zoom levels than in Google/Bing map, this is because some of our map tile layers in our applications cannot visible properly in last "*zoom In*" level. Is it possible ?

Thanks . It is working. I added two more zoom levels in my own tile layer. And using zoom event handler ,
I switched of Bing tile layer if it zoomed in level 19.
Zoom Level details are given below
<zoom_levels levels="21" min_scale="0.0" max_scale="0.0" min_tile_width="19.109256744384766" min_tile_height="2.0037508E7">
<zoom_level level="0" name="" description="" scale="0.0" tile_width="2.0037508E7" tile_height="2.0037508E7"/>
<zoom_level level="1" name="" description="" scale="0.0" tile_width="1.0018754E7" tile_height="1.0018754E7"/>
<zoom_level level="2" name="" description="" scale="0.0" tile_width="5009377.0" tile_height="5009377.0"/>
<zoom_level level="3" name="" description="" scale="0.0" tile_width="2504688.5" tile_height="2504688.5"/>
<zoom_level level="4" name="" description="" scale="0.0" tile_width="1252344.25" tile_height="1252344.25"/>
<zoom_level level="5" name="" description="" scale="0.0" tile_width="626172.125" tile_height="626172.125"/>
<zoom_level level="6" name="" description="" scale="0.0" tile_width="313086.0625" tile_height="313086.0625"/>
<zoom_level level="7" name="" description="" scale="0.0" tile_width="156543.03125" tile_height="156543.03125"/>
<zoom_level level="8" name="" description="" scale="0.0" tile_width="78271.515625" tile_height="78271.515625"/>
<zoom_level level="9" name="" description="" scale="0.0" tile_width="39135.7578125" tile_height="39135.7578125"/>
<zoom_level level="10" name="" description="" scale="0.0" tile_width="19567.87890625" tile_height="19567.87890625"/>
<zoom_level level="11" name="" description="" scale="0.0" tile_width="9783.939453125" tile_height="9783.939453125"/>
<zoom_level level="12" name="" description="" scale="0.0" tile_width="4891.9697265625" tile_height="4891.9697265625"/>
<zoom_level level="13" name="" description="" scale="0.0" tile_width="2445.98486328125" tile_height="2445.98486328125"/>
<zoom_level level="14" name="" description="" scale="0.0" tile_width="1222.992431640625" tile_height="1222.992431640625"/>
<zoom_level level="15" name="" description="" scale="0.0" tile_width="611.4962158203125" tile_height="611.4962158203125"/>
<zoom_level level="16" name="" description="" scale="0.0" tile_width="305.74810791015625" tile_height="305.74810791015625"/>
<zoom_level level="17" name="" description="" scale="0.0" tile_width="152.87405395507812" tile_height="152.87405395507812"/>
<zoom_level level="18" name="" description="" scale="0.0" tile_width="76.43702697753906" tile_height="76.43702697753906"/>
<zoom_level level="19" name="" description="" scale="0.0" tile_width="38.21851348876953" tile_height="38.21851348876953"/>
<zoom_level level="20" name="" description="" scale="0.0" tile_width="19.109256744384766" tile_height="19.109256744384766"/>
</zoom_levels>
Thank you Jayant

Similar Messages

Google maps don't display right, part is good but about half of it says "we are sorry, but we don't have maps at this zoom level for this region." Zooming out doesn't help.

When displaying a Google map I get about four vertical strips that alternately display good and in gray bands. The gray area displays the message "we are sorry, but we don't have maps at this zoom level for this region." Zooming out doesn't get rid of the gray areas.
I've had this problem for over a year and get around it by using either MS Internet Explorer or Google Chrome which work Ok. Otherwise Firefox works fine and I use it for everything else except Google Maps.
I've tried an uninstall of FireFox and then reinstall but it didn't help. I don't remember what I was doing when this problem first showed up.

You're welcome

Zoom level in WPF Application consuming Bing Maps Web Services

Hi,
I am having trouble in setting the zoom level for the map with 7 pushpins (P1 through P7). The map is centered with point P1. I want all the push pins to show on the map. I have set the zoom level as follows.
Zoom Level 15 - if the points (P2...P7) are within 1 mile from P1
Zoom Level 14 - if the points (P2...P7) are between 1.1 and 1.5 miles from P1
Zoom Level 10 - if the points (P2...P7) are > 1.5 miles from P1.
If there a better way (like autozoom) to do this?
Thanks.
Regards, Venkat

Rick,
I have attached the map generated using SOAP services.
I tried to generate the same map using REST services as follows.
http://dev.virtualearth.net/REST/v1/Imagery/Map/Road?mapSize=640,480&pp=36.150928,-83.439971;10;S&pp=36.171645820140839,-83.410888686776161;32;S1&pp=36.168693,-83.415779;32;S2&pp=36.185192,-83.435401;32;S3&pp=36.140907,-83.472549;23;L1&pp=36.174339,-83.425415;23;L2&pp=36.17805,-83.433433;23;L3&key=BingKey&format=jpeg
The REST services map looks like its zoomed in compared to the SOAP services map. However the road/street names are missing. Is there any way to get the road/street names in the REST services map like in the online bing maps? Please advise.
SOAP SERVICES MAP
REST SERVICES MAP
Regards, Venkat

How to hold back zoom level setting?

Zoom level changes every time with opening page, & I want to keep already set zoom level ,as it happens in other browsers like Google Crome.How to keep zoom level always set ,at it's selected level? I tried with add on to solve this,but result was not so good.Hopefully you will help me...I enjoy FIREFOX..Thank you.

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: 
https://addons.mozilla.org/en-US/firefox/addon/6965
Or the NoSquint extension: 
https://addons.mozilla.org/en-US/firefox/addon/2592/

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.

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.

Displaying report in PDF with Zoom level at 100%

Hi,
I am using ReportDocument.ExportToHttpResponse() to export the desired reports to the PDF format. The report is being displayed on the screen immediately. I want to show the report at 100% zoom level every time the user export the report. My existing code segment for this purpose as follows:
                ExportOptions exportOpts = new ExportOptions();
                PdfFormatOptions pdfOpts = ExportOptions.CreatePdfFormatOptions();
                pdfOpts.UsePageRange = true;
                pdfOpts.FirstPageNumber = 2;
                pdfOpts.LastPageNumber = Int32.MaxValue;
                exportOpts.ExportFormatType = ExportFormatType.PortableDocFormat;
                exportOpts.ExportFormatOptions = pdfOpts;
                rptDoc.ExportToHttpResponse(exportOpts, Response, false, "");
tried to find out any related setting in PdfFormatOptions object but to no avail. Please suggest any possible option to force the viewer to open the report at 100%.
Regards,
Ali
Edited by: ali.net on Jan 11, 2012 2:17 PM

Hi Ali,
Please refer to the 'Rules of Engagement' alwas provide enough information.
- Version of Crystal Reports with detail patch level.
- Version of Visual Studio
- Do you see the same behaviour when the report is exported from CR viewer export button?
- Try using [ExportToStream|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333133393338333533383337%7D.do]
rd.ExportToDisk(ExportFormatType.PortableDocFormat, "C:
ep1.pdf");
See if it reproduces the issue.
- Bhushan.

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.'''

Im looking for a replacement of "Default Zoom Level" addon.

Im looking for a replacement of "Default Zoom Level" addon. Why is this disabled in Firefox 5/6? Is there a similar addon or how can I set the default zoom?

Did you do a compatibility check?
That is required in cases where the extension has a maxVersion (in this case 4.0.*) set in the XPI file and the server has the correct compatibility data ([[https://versioncheck.addons.mozilla.org/update/VersionCheck.php?reqVersion=2&id={D9A7CBEC-DE1A-444f-A092-844461596C4D}&version=4.5&maxAppVersion=6.0&status=userEnabled&appID={ec8030f7-c20a-464f-9b0e-13a3a9e97384}&appVersion=5.0&appOS=Windows&appABI=x86-msvc&locale=en-US&currentAppVersion=5.0&updateType=97 8.*]]).
From https://addons.mozilla.org/en-US/firefox/addon/default-fullzoom-level/ 
Works with: Firefox 3.6 - 8.*

Different zoom levels for different clips in the same project?

Hi
I am making a movie with videos from two different cameras. As a result some of the clips are cut down in size to a small portion of the screen. This can be solved if it is possible to use different zoom levels for different clips in the same project. I have not been able to do this. Is it possible?
kind regards
Soren

You can scale the small clips up to the same size of the larger one... but you will get a quality loss.
Using Motion or Scale to Frame Size commands
Better to scale the large ones down to a Sequence that matches the smaller clip dimensions.

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.

Hi, how can I keep the same zoom level for all the pages I view in Safari and even when I close and open it. Indeed with a 27 inch Imac I have a lot of space, most of the websites are built for smaller resolutions and my sight is dropping !   Thx

Hi, how can I keep the same zoom level for all the pages I view in Safari and even when I close and open it. Indeed with a 27 inch Imac I have a lot of space, most of the websites are built for smaller resolutions and my sight is dropping !   Thx

Hi, how can I keep the same zoom level for all the pages I view in Safari and even when I close and open it. Indeed with a 27 inch Imac I have a lot of space, most of the websites are built for smaller resolutions and my sight is dropping !   Thx

Google/Bing Zoom Level

Similar Messages

Maybe you are looking for