The work around would be to either set a uniform color background in your PDF viewer, or make PDF viewer narrower so that the background on each side of the page is not showing, and setting the viewer to show continuous pages (so that no background is shown between the pages). The problem is similar if you have some part that are animated fast or change the image before and after scroll. If some part of the window moves, and another (background) does not move, such comparison will fail, as there is no identical parts before and after the scroll. The reason is that HyperSnap has to compare the images before and after each scroll, to find identical parts and what was added at the bottom, to correctly stitch the images. If you capture something that is not uniform color and does not scroll with the rest of the window, auto-scroll will not work. Capturing PDF documents with scrolling fails The reason you sometimes cannot capture PDF documents with scrolling is due to the background behind the pages in a PDF viewer, which has some kind of pattern or shading, but does not move as you scroll the pages. To capture fully a web page from the most popular browsers, you don't need HyperSnap anymore. Workarounds include using “scroll region” function and carefully outlining what you want to capture with scrolling, avoiding non-scrolling elements (e.g. If your page has contents that animates quickly, or elements that don’t scroll, just stay in place, any such comparison will fail and I cannot fix it. I'm often asked why scrolling capture fails for many web pages, so decided to post this and the possible workarounds: Scrolling capture relies on capturing the visible part of a page, scrolling it a little bit, capturing again and comparing the two to find how much the contents has moved. Scrolling capture fails for many web pages, PDF docs etc.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |