Note that there are some explanatory texts on larger screens.

plurals
  1. POUIScrollView doesn't work properly (it backs to top and not shows any scrollers
    primarykey
    data
    text
    <p>I'm doing an iphone app where I've severals UILabels, UITextfields and UIButtons. I need show them in a screen with more 480px of height, so I've introducing them into an UIView. Later, I've created an UIScroller for show them.</p> <p>Its struct in interface builder is:</p> <ul> <li>View controller <ul> <li>---> View (it isn't resizable and may be obligatory) <ul> <li>---> Scrollview <ul> <li>---> View <ul> <li>---> Labels</li> <li>---> TextFields</li> </ul></li> </ul></li> </ul></li> </ul></li> </ul> <p>I've set UIScrollView contentsize's and UIView frame below "User Defined Runtine Attributes" in "Identity Inspector" (on Interface Builder) and show them in Console Log when app runs. Seems be ok, but UIScrollView always back to top when I scroll it down and its scrolls weren't shown.</p> <p>I've search a lot in this forum I haven't found any solution.</p> <p>Can anybody help me? Thanks!</p> <p>Edit: I added on my code this to show their defined values (uploadView is the view in scrollView)</p> <pre><code>- (void) viewDidLoad { //.... [super viewDidLoad]; CGSize size = scrollView.contentSize; CGRect viewrect = uploadView.frame; CGSize viewsize = viewrect.size; NSLog (@"size of scrollView: height= %f and width= %f", size.height, size.width); NSLog (@"size of uploadView: height= %f and width= %f", viewsize.height, viewsize.width); </code></pre> <p>}</p> <p>The outputs are:</p> <pre><code>size of scrollview: height= 600.000000 and width= 320.0000000 size of uploadview: height= 600.000000 and width= 320.0000000 </code></pre>
    singulars
    1. This table or related slice is empty.
    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. This table or related slice is empty.
 

Querying!

 
Guidance

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