Menu
I have an Objective-C project I'm refactoring and I've enountered a line that I can't translate and Apple's documentation site seems to be down:
[self.stepperView setFrame:self.stepperView.frame];
I've tried this:
self.stepperView.frame = stepperView.frame
but the view is still getting drawn in the wrong spot. Does anyone know the setFrame equivalent in Swift?
I tried looking at Apple's documentation, but it seems the site is down:
983
Frame A view's frame ( CGRect ) is the position of its rectangle in the superview 's coordinate system. By default it starts at the top left. Bounds A view's bounds ( CGRect ) expresses a view rectangle in its own coordinate system.
1) Control-drag from a frame view (e.g. questionFrame) to main View, in the pop-up select "Equal heights". 2)Then go to size inspector of the frame, click edit "Equal height to Superview" constraint, set the multiplier to 0.7 and hit return.
frame = a view's location and size using the parent view's coordinate system ( important for placing the view in the parent) bounds = a view's location and size using its own coordinate system (important for placing the view's content or subviews within itself)
Views are the fundamental building blocks of your app's user interface, and the UIView class defines the behaviors that are common to all views. A view object renders content within its bounds rectangle, and handles any interactions with that content.
setFrame and frame are equivalent in Objective-C and Swift.
In Objective-C, setFrame is the generated setter method for a property. You can also do (in Objective-C) view.frame = someFrame which is 100% the same as calling setFrame: it's just a matter of which syntax you prefer.
In Swift, all the setVariable: method names are replaced with the dot-syntax equivalent of view.frame = ....
As far as why your view is getting drawn in the wrong spot, you'd have to post a concrete example of how you're placing your view. It's most likely a math or calculation error. It's also worth noting that the iOS coordinate layout has y-values increasing as you go down, unlike typical Cartesian coordinates.
I also noticed that in one of the tabs in your screenshot that you searched "unable to set frame before viewDidLoad". viewDidLoad is the wrong place to be setting any frame values. According to the documentation:
This method is called after the view controller has loaded its view hierarchy into memory. This method is called regardless of whether the view hierarchy was loaded from a nib file or created programmatically in the loadView method. You usually override this method to perform additional initialization on views that were loaded from nib files.
which means viewDidLoad is the place for initialization of state, variables, whatever but not the place for layout because it's incredibly likely that somewhere in between viewDidLoad and viewDidAppear that something else, something out of your control is re-positioning your view. The most likely culprit is the view bounds changing and adjusting all subviews.
132
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
