Skip to main content

UIScrollView not scrolling although contentSize is smaller than UIImageView



So I have a UIImageView as a subview of UIScrollView, I've set the contentSize to be smaller than the UIImageView width and height, however it doesn't allow me to scroll.. why is this? Here's some code:







UIImage * image = [UIImage imageWithData:data];

UIImageView * imgView = [[UIImageView alloc] initWithImage:image];

[imgView setUserInteractionEnabled:YES];

//[imgView setContentMode:UIViewContentModeScaleAspectFill];

[imgView setBackgroundColor:[UIColor clearColor]];

[imgView setAutoresizingMask:UIViewAutoresizingFlexibleWidth | UIViewAutoresizingFlexibleHeight];

[imgView setFrame:CGRectMake(0, 0, imgView.frame.size.width, imgView.frame.size.height)];



CGRect imgFrame;

imgFrame.size.width = originalImageSize.width;

imgFrame.size.height = originalImageSize.height;

imgFrame.origin.x = imageOriginPoint.x;

imgFrame.origin.y = imageOriginPoint.y;



UIScrollView * imgScrollView = [[UIScrollView alloc] initWithFrame:imgFrame];

[imgScrollView setScrollEnabled:YES];

[imgScrollView setClipsToBounds:YES];

[imgScrollView addSubview:imgView];

[imgScrollView setBackgroundColor:[UIColor clearColor]];





[imgScrollView setFrame:imgFrame];

[imgScrollView setContentSize:CGSizeMake(200, 200)];



SCROLL VIEW CONTENT SIZE WIDTH IS 200.000000 AND HEIGHT CONTENT SIZE IS 200.000000

UIIMAGE VIEW WIDTH IS 2240.225830 AND HEIGHT IS 2240.225830

SCROLL VIEW FRAME WIDTH IS 768.000000 AND SCROLL VIEW FRAME HEIGHT IS 768.000061







Any idea?


Comments

  1. That's because that your size of bounds of scroll view is larger than your content size.
    The content size need to be the actual size of image view, and the visible size is set by frame / bounds. I guess you want to scroll a image in a {200, 200} sized rect?
    Try this:

    UIScrollView * imgScrollView = [[UIScrollView alloc] initWithFrame:CGRectMake(0, 0, 200, 200)]; // this is your visible rect
    [imgScrollView setScrollEnabled:YES];
    [imgScrollView setClipsToBounds:YES];
    [imgScrollView addSubview:imgView];
    [imgScrollView setBackgroundColor:[UIColor yellowColor]];

    [imgScrollView setContentSize:imgFrame.size]; // this is your image view size

    ReplyDelete
  2. scroll view content size should be more than scrollView frame width and height
    do this -

    scrollView.contentSize = CGSizeMake(originalImageSize.width,originalImageSize.height);


    I think it will help.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex