Databases
StackOverflow2013
Postsdbo
POCATiledLayer being removed and refreshed while zoomed in iPad 3rd gen
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCATiledLayer being removed and refreshed while zoomed in iPad 3rd gen
    primarykey
    data
    text
    <p>I'm experiencing a redraw problem on a CATiledLayer when the parent UIScrollView is zoomed in.</p> <p>I'm rendering a PDF page in a CATiledLayer backed UIView. It has another UIImageView behind it, which contains a low-res image of the page that the CATiledLayer will draw. When I zoom in, it works as expected. The CATiledLayer will render a higher resolution image according to the zoom level. </p> <p>The problem occurs after zooming. If I zoom in then just leave the iPad alone, the displayed image blurs then resharpens. It looks like the CATiledLayer is being removed, since I see the blurry low resolution image in the backing view, then the CATiledLayer gets redrawn, i.e. I see the tiling effect and the resharpening of the image. This happens if I just leave the app alone and wait about 30 to 40 seconds. I've only observed it on the iPad 3rd gen (New iPad, iPad3, whatever). I'm also testing on iPad2s and I have yet to encounter the issue.</p> <p>Has anyone else encountered this problem? Any known cause and, possibly, solutions?</p> <p>Edit: </p> <p>My UIScrollViewDelegate methods are as follows:</p> <pre><code>// currentPage, previousPage, and nextPage are the pdf page views // that are having the refresh problem - (void)positionBufferedPages { // performs math {code omitted} // then sets the center of the views [previousPage.view setCenter:...]; [nextPage.view setCenter:...]; } - (void)hideBufferedPages { if ([previousPage.view isDescendantOfView:scrollView]) { [previousPage.view removeFromSuperview]; } if ([nextPage.view isDescendantOfView:scrollView]) { [nextPage.view removeFromSuperview]; } } - (void)showBufferedPages { if (![previousPage.view isDescendantOfView:scrollView]) { [scrollView addSubview:previousPage.view]; } if (![nextPage.view isDescendantOfView:scrollView]) { [scrollView addSubview:nextPage.view]; } if (![currentPage.view isDescendantOfView:scrollView]) { [scrollView addSubview:currentPage.view]; } } - (UIView *)viewForZoomingInScrollView:(UIScrollView *)scrollView { return currentPage.view; } - (void)scrollViewWillBeginZooming:(UIScrollView *)scrollView withView:(UIView *)view { [self hideBufferedPages]; } - (void)scrollViewDidEndZooming:(UIScrollView *)scrollViewParam withView:(UIView *)view atScale:(float)scale { [self positionBufferedPages]; [self showBufferedPages]; } - (void)scrollViewDidZoom:(UIScrollView *)scrollView { // nothing relating to the pdf page view // but does set the center of some other subviews on top of the pdf page views } </code></pre> <p>Not sure how helpful this will be though, as the scrollview is not receiving input while the problem happens. As mentioned above, the pdf page is loaded to the CATiledLayer, then I leave the iPad alone (no input is received by the device), and the CATiledLayer will redraw by itself.</p> <p>I've also tried catching calls to <code>setNeedsDisplay</code>, <code>setNeedsDisplayInRect:</code>, <code>setNeedsLayout</code>, and <code>setNeedsDisplayOnBoundsChange:</code> on both the view and the tiled layer, but the redraw happens without any of those functions getting called. <code>drawLayer:inContext:</code> gets called, of course, but the trace only shows some Quartz calls being started in a background thread (as expected, as tiled layers prepare the content in the background), so it is of no help either.</p> <p>Thanks in advance!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAltealice
    1. USAltealice
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCATiledLayer being removed and refreshed while zoomed in iPad 3rd gen
      1. USAltealice
      1. VTBountyStart
    2. VO
      singulars
      1. POCATiledLayer being removed and refreshed while zoomed in iPad 3rd gen
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCATiledLayer being removed and refreshed while zoomed in iPad 3rd gen
      1. USChris Wagner
      1. VTFavorite
    1. COCould it be because of the hi-res retina display of the ipad 3? Are you setting the CATiledLayer contentsScale correctly? Also in your custom PDF creation rendering code you should be using UIGraphicsBeginImageContextWithOptions and set the scale accordingly
      singulars
      1. POCATiledLayer being removed and refreshed while zoomed in iPad 3rd gen
      1. USLefteris
    2. COI'm not using UIGraphicsBeginImageContextWithOptions, but I use CGContextScaleCTM to set the scale. Is there a difference? It looks like I'm rendering the pdf properly. My problem is that the CATiledLayer somehow redraws itself for no reason after a while.
      singulars
      1. POCATiledLayer being removed and refreshed while zoomed in iPad 3rd gen
      1. USAltealice
    3. COYou should set the CATiledLayer contentsScale to the [[UIScreen mainScreen] scale]
      singulars
      1. POCATiledLayer being removed and refreshed while zoomed in iPad 3rd gen
      1. USLefteris
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload