Mixing
![Cross-Platform Console Clearing? [duplicate]](https://lh4.googleusercontent.com/-2wSRBbRX4Os/AAAAAAAAAAI/AAAAAAAAAVo/JonVpMrIgFI/s72-c/photo.jpg?sz=32)
Xcode: Setting width and height in Utilities / Size / View versus as a constraint
I'm an iOS and XCode beginner. I'm trying to set a button to have dimensions of 64 x 64. In searching how this is done, I've come across two different ways:
- Select the button, and in the Utilities pane's Size inspector's View section, set the height and width.
- In the bottom right corner of the storyboard pane, click the "Add New Constraints" button, check "Width" and "Height" and set them to the desired dimensions. This adds
Constraintsindented under the button, withheight = 64andwidth = 64indented underConstraints.
Both seem to work fine, so my question is what is the difference between the two methods, if any?
ios xcode
asked Jan 1 at 20:32
VincentVincent
1,27911425
add a comment |
I'm an iOS and XCode beginner. I'm trying to set a button to have dimensions of 64 x 64. In searching how this is done, I've come across two different ways:
- Select the button, and in the Utilities pane's Size inspector's View section, set the height and width.
- In the bottom right corner of the storyboard pane, click the "Add New Constraints" button, check "Width" and "Height" and set them to the desired dimensions. This adds
Constraintsindented under the button, withheight = 64andwidth = 64indented underConstraints.
Both seem to work fine, so my question is what is the difference between the two methods, if any?
ios xcode
asked Jan 1 at 20:32
VincentVincent
1,27911425
add a comment |
I'm an iOS and XCode beginner. I'm trying to set a button to have dimensions of 64 x 64. In searching how this is done, I've come across two different ways:
- Select the button, and in the Utilities pane's Size inspector's View section, set the height and width.
- In the bottom right corner of the storyboard pane, click the "Add New Constraints" button, check "Width" and "Height" and set them to the desired dimensions. This adds
Constraintsindented under the button, withheight = 64andwidth = 64indented underConstraints.
Both seem to work fine, so my question is what is the difference between the two methods, if any?
ios xcode
asked Jan 1 at 20:32
VincentVincent
1,27911425
I'm an iOS and XCode beginner. I'm trying to set a button to have dimensions of 64 x 64. In searching how this is done, I've come across two different ways:
- Select the button, and in the Utilities pane's Size inspector's View section, set the height and width.
- In the bottom right corner of the storyboard pane, click the "Add New Constraints" button, check "Width" and "Height" and set them to the desired dimensions. This adds
Constraintsindented under the button, withheight = 64andwidth = 64indented underConstraints.
Both seem to work fine, so my question is what is the difference between the two methods, if any?
ios xcode
ios xcode
asked Jan 1 at 20:32
VincentVincent
1,27911425
asked Jan 1 at 20:32
VincentVincent
1,27911425
edited Jan 4 at 3:20
Vincent
asked Jan 1 at 20:32
VincentVincent
1,27911425
asked Jan 1 at 20:32
VincentVincent
1,27911425
asked Jan 1 at 20:32
VincentVincent
1,27911425
1,27911425
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
First of all welcome to iOS development :)
The answer is: In case 2 you are using Autolayout and in case 1 you are not.
Autolayout is really important and you should definitely always use it. The constraints allow you to create "rules" that tell the app how to adjust the UI to different screen sizes. In your case the button might have the same size for all screens, but without setting the constraints the size might change nevertheless depending on the layout of the constraints of other UI Components.
I recommend reading a tutorial about Autolayout. It is easy to learn and hard to master I would say...
answered Jan 1 at 23:18
Robin BorkRobin Bork
1326
add a comment |
While you're building your interface check the Document Outline to the left of the Storyboard for warnings, usually this is a strong indicator of areas of concern as your application begins to grow. Rule of thumb is when in doubt add constraints.
Also worth mentioning for your 64x64 (square) example.. I personally like using a 1:1 aspect ratio constraint plus a height or width constraint so if theres ever a need to scale the view its one constraint value to modify instead of two.
answered Jan 3 at 17:02
mikebobmikebob
37627
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53998737%2fxcode-setting-width-and-height-in-utilities-size-view-versus-as-a-constrain%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
First of all welcome to iOS development :)
The answer is: In case 2 you are using Autolayout and in case 1 you are not.
Autolayout is really important and you should definitely always use it. The constraints allow you to create "rules" that tell the app how to adjust the UI to different screen sizes. In your case the button might have the same size for all screens, but without setting the constraints the size might change nevertheless depending on the layout of the constraints of other UI Components.
I recommend reading a tutorial about Autolayout. It is easy to learn and hard to master I would say...
answered Jan 1 at 23:18
Robin BorkRobin Bork
1326
add a comment |
First of all welcome to iOS development :)
The answer is: In case 2 you are using Autolayout and in case 1 you are not.
Autolayout is really important and you should definitely always use it. The constraints allow you to create "rules" that tell the app how to adjust the UI to different screen sizes. In your case the button might have the same size for all screens, but without setting the constraints the size might change nevertheless depending on the layout of the constraints of other UI Components.
I recommend reading a tutorial about Autolayout. It is easy to learn and hard to master I would say...
answered Jan 1 at 23:18
Robin BorkRobin Bork
1326
add a comment |
First of all welcome to iOS development :)
The answer is: In case 2 you are using Autolayout and in case 1 you are not.
Autolayout is really important and you should definitely always use it. The constraints allow you to create "rules" that tell the app how to adjust the UI to different screen sizes. In your case the button might have the same size for all screens, but without setting the constraints the size might change nevertheless depending on the layout of the constraints of other UI Components.
I recommend reading a tutorial about Autolayout. It is easy to learn and hard to master I would say...
answered Jan 1 at 23:18
Robin BorkRobin Bork
1326
First of all welcome to iOS development :)
The answer is: In case 2 you are using Autolayout and in case 1 you are not.
Autolayout is really important and you should definitely always use it. The constraints allow you to create "rules" that tell the app how to adjust the UI to different screen sizes. In your case the button might have the same size for all screens, but without setting the constraints the size might change nevertheless depending on the layout of the constraints of other UI Components.
I recommend reading a tutorial about Autolayout. It is easy to learn and hard to master I would say...
answered Jan 1 at 23:18
Robin BorkRobin Bork
1326
answered Jan 1 at 23:18
Robin BorkRobin Bork
1326
answered Jan 1 at 23:18
Robin BorkRobin Bork
1326
answered Jan 1 at 23:18
Robin BorkRobin Bork
1326
1326
add a comment |
add a comment |
While you're building your interface check the Document Outline to the left of the Storyboard for warnings, usually this is a strong indicator of areas of concern as your application begins to grow. Rule of thumb is when in doubt add constraints.
Also worth mentioning for your 64x64 (square) example.. I personally like using a 1:1 aspect ratio constraint plus a height or width constraint so if theres ever a need to scale the view its one constraint value to modify instead of two.
answered Jan 3 at 17:02
mikebobmikebob
37627
add a comment |
While you're building your interface check the Document Outline to the left of the Storyboard for warnings, usually this is a strong indicator of areas of concern as your application begins to grow. Rule of thumb is when in doubt add constraints.
Also worth mentioning for your 64x64 (square) example.. I personally like using a 1:1 aspect ratio constraint plus a height or width constraint so if theres ever a need to scale the view its one constraint value to modify instead of two.
answered Jan 3 at 17:02
mikebobmikebob
37627
add a comment |
While you're building your interface check the Document Outline to the left of the Storyboard for warnings, usually this is a strong indicator of areas of concern as your application begins to grow. Rule of thumb is when in doubt add constraints.
Also worth mentioning for your 64x64 (square) example.. I personally like using a 1:1 aspect ratio constraint plus a height or width constraint so if theres ever a need to scale the view its one constraint value to modify instead of two.
answered Jan 3 at 17:02
mikebobmikebob
37627
While you're building your interface check the Document Outline to the left of the Storyboard for warnings, usually this is a strong indicator of areas of concern as your application begins to grow. Rule of thumb is when in doubt add constraints.
Also worth mentioning for your 64x64 (square) example.. I personally like using a 1:1 aspect ratio constraint plus a height or width constraint so if theres ever a need to scale the view its one constraint value to modify instead of two.
answered Jan 3 at 17:02
mikebobmikebob
37627
answered Jan 3 at 17:02
mikebobmikebob
37627
answered Jan 3 at 17:02
mikebobmikebob
37627
answered Jan 3 at 17:02
mikebobmikebob
37627
37627
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53998737%2fxcode-setting-width-and-height-in-utilities-size-view-versus-as-a-constrain%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
