Just a quick question: what options are supported for the embedded cloud-hosted Viewer when it comes to rendering files? I’m aware of the “quality” option which is a value from 0 to 100 (which apparently signifies the level of fidelity you want the output to be with regards to the input file). I also see that there is a “use_pdf” option; what does that do exactly? My colleagues and I noticed that even with quality=100, many Microsoft Excel files were completely pixelated and un-readable, but once I flipped the “use_pdf” option from “False” to “True”, the quality improved many times over and the file was very readable.
The issues you have found earlier (filed as WEB-2102) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by GroupDocsNotifier.
Great; I’m glad to hear that I’m using those options correctly.
Thanks for giving this your attention. Also on the topic of the Viewer’s options, is it possible to turn off the search bar? In my company’s testing, we found that the search function is not very consistent and often either does not work or it highlights the wrong portions of documents. We therefore would like to disable searching entirely before we expose the viewer to our clients.
Hi, here are some of the use-cases that I am referring to:
- Sometimes, the search simply doesn’t do anything. There are no errors in the browser’s console log. Please refer to this video. In this video, I have compared the behavior of the Mac OS X Preview application with the GroupDocs viewer functionality for a single PDF file. As you can see, the document is searchable with the Preview application, but not with the GroupDocs Viewer. You can view the iframe source here.
- Other times (and I haven’t managed to capture video footage of it, but I have seen it, as have many other individuals within my company in their own testing), the text highlighting will be off. It’s difficult to describe, but the areas of the document that end up highlighted by the search feature will not correspond to the text searched for. Generally, it will be close, but the actual highlighting will be shifted some number of pixels off-target. If I manage to get video recording of this issue, I will post it here.=
Thanks for catching the encoded characters in the query string; I think it got messed up when copy-pasting on my side.
Huh, really? I don’t see that information anywhere.