Xcode IB warns about ambiguous position for UIStackView in UICollectionViewCell though it shouldn't beHow to use auto-layout to move other views when a view is hidden?UIScrollView Scrollable Content Size AmbiguityEmulating aspect-fit behaviour using AutoLayout constraints in Xcode 6Xcode - Width and Horizontal Position Are AmbiguousChange size of uiview with auto layout and make it always in centeredCenter UIView inside UIScrollView using AutoLayout in the interface builder onlyKeep UIDatePicker from Growing too WideProblems when trying to hide a UIStackView's subviewWhy is the vertical position for this view ambiguous?How to set the scrollview height when UI elements are dynamically created
Is this a crack on the carbon frame?
What do the dots in this tr command do: tr .............A-Z A-ZA-Z <<< "JVPQBOV" (with 13 dots)
Can a Warlock become Neutral Good?
Smoothness of finite-dimensional functional calculus
"to be prejudice towards/against someone" vs "to be prejudiced against/towards someone"
An academic/student plagiarism
Is it important to consider tone, melody, and musical form while writing a song?
Have astronauts in space suits ever taken selfies? If so, how?
Why do falling prices hurt debtors?
The use of multiple foreign keys on same column in SQL Server
Is it possible to do 50 km distance without any previous training?
Modeling an IPv4 Address
Risk of getting Chronic Wasting Disease (CWD) in the United States?
How does strength of boric acid solution increase in presence of salicylic acid?
Is it legal for company to use my work email to pretend I still work there?
Test whether all array elements are factors of a number
Adding span tags within wp_list_pages list items
Why Is Death Allowed In the Matrix?
strToHex ( string to its hex representation as string)
Why do I get two different answers for this counting problem?
To string or not to string
Which models of the Boeing 737 are still in production?
Do I have a twin with permutated remainders?
How to write a macro that is braces sensitive?
Xcode IB warns about ambiguous position for UIStackView in UICollectionViewCell though it shouldn't be
How to use auto-layout to move other views when a view is hidden?UIScrollView Scrollable Content Size AmbiguityEmulating aspect-fit behaviour using AutoLayout constraints in Xcode 6Xcode - Width and Horizontal Position Are AmbiguousChange size of uiview with auto layout and make it always in centeredCenter UIView inside UIScrollView using AutoLayout in the interface builder onlyKeep UIDatePicker from Growing too WideProblems when trying to hide a UIStackView's subviewWhy is the vertical position for this view ambiguous?How to set the scrollview height when UI elements are dynamically created
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I tried trailing,leading,bottom,top as well as center/width/height constraint-sets. In both cases Xcode complains about ambiguous position unless I wrap the stackview in a UIView inside the cell.
Is this supposed to work like this or am I missing something?
ios xcode interface-builder
add a comment |
I tried trailing,leading,bottom,top as well as center/width/height constraint-sets. In both cases Xcode complains about ambiguous position unless I wrap the stackview in a UIView inside the cell.
Is this supposed to work like this or am I missing something?
ios xcode interface-builder
add a comment |
I tried trailing,leading,bottom,top as well as center/width/height constraint-sets. In both cases Xcode complains about ambiguous position unless I wrap the stackview in a UIView inside the cell.
Is this supposed to work like this or am I missing something?
ios xcode interface-builder
I tried trailing,leading,bottom,top as well as center/width/height constraint-sets. In both cases Xcode complains about ambiguous position unless I wrap the stackview in a UIView inside the cell.
Is this supposed to work like this or am I missing something?
ios xcode interface-builder
ios xcode interface-builder
edited Mar 22 at 5:11
Martin
asked Mar 21 at 23:53
MartinMartin
303316
303316
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You have too many constraints and they likely conflict. The system needs one position and one size for each dimension. If you give it two positions then it automatically infers the dimension -- ie if you give it top and bottom then it auto calculates the height, so you shouldn't also be specifying the height. On top of that the stack view can actually determine its own height if all of its elements have an intrinsic size. In that case you can just specify a single position constraint.
TLDR just use top, bottom, leading, trailing constraints and the system will infer the width and height.
I'm sorry if my phrasing was ambiguous. I was referring to the sets of top/bottom/leading/trailing and center/width/height separately, of course.
– Martin
Mar 22 at 5:10
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%2f55290903%2fxcode-ib-warns-about-ambiguous-position-for-uistackview-in-uicollectionviewcell%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You have too many constraints and they likely conflict. The system needs one position and one size for each dimension. If you give it two positions then it automatically infers the dimension -- ie if you give it top and bottom then it auto calculates the height, so you shouldn't also be specifying the height. On top of that the stack view can actually determine its own height if all of its elements have an intrinsic size. In that case you can just specify a single position constraint.
TLDR just use top, bottom, leading, trailing constraints and the system will infer the width and height.
I'm sorry if my phrasing was ambiguous. I was referring to the sets of top/bottom/leading/trailing and center/width/height separately, of course.
– Martin
Mar 22 at 5:10
add a comment |
You have too many constraints and they likely conflict. The system needs one position and one size for each dimension. If you give it two positions then it automatically infers the dimension -- ie if you give it top and bottom then it auto calculates the height, so you shouldn't also be specifying the height. On top of that the stack view can actually determine its own height if all of its elements have an intrinsic size. In that case you can just specify a single position constraint.
TLDR just use top, bottom, leading, trailing constraints and the system will infer the width and height.
I'm sorry if my phrasing was ambiguous. I was referring to the sets of top/bottom/leading/trailing and center/width/height separately, of course.
– Martin
Mar 22 at 5:10
add a comment |
You have too many constraints and they likely conflict. The system needs one position and one size for each dimension. If you give it two positions then it automatically infers the dimension -- ie if you give it top and bottom then it auto calculates the height, so you shouldn't also be specifying the height. On top of that the stack view can actually determine its own height if all of its elements have an intrinsic size. In that case you can just specify a single position constraint.
TLDR just use top, bottom, leading, trailing constraints and the system will infer the width and height.
You have too many constraints and they likely conflict. The system needs one position and one size for each dimension. If you give it two positions then it automatically infers the dimension -- ie if you give it top and bottom then it auto calculates the height, so you shouldn't also be specifying the height. On top of that the stack view can actually determine its own height if all of its elements have an intrinsic size. In that case you can just specify a single position constraint.
TLDR just use top, bottom, leading, trailing constraints and the system will infer the width and height.
answered Mar 22 at 3:58
Josh HomannJosh Homann
9,11711421
9,11711421
I'm sorry if my phrasing was ambiguous. I was referring to the sets of top/bottom/leading/trailing and center/width/height separately, of course.
– Martin
Mar 22 at 5:10
add a comment |
I'm sorry if my phrasing was ambiguous. I was referring to the sets of top/bottom/leading/trailing and center/width/height separately, of course.
– Martin
Mar 22 at 5:10
I'm sorry if my phrasing was ambiguous. I was referring to the sets of top/bottom/leading/trailing and center/width/height separately, of course.
– Martin
Mar 22 at 5:10
I'm sorry if my phrasing was ambiguous. I was referring to the sets of top/bottom/leading/trailing and center/width/height separately, of course.
– Martin
Mar 22 at 5:10
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%2f55290903%2fxcode-ib-warns-about-ambiguous-position-for-uistackview-in-uicollectionviewcell%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