On 19 Sep 2013, at 7:37 PM, Rick Mann <rm...@latencyzero.com> wrote:
>
> On Sep 19, 2013, at 17:36 , Kyle Sluder <k...@ksluder.com> wrote:
>
>> Is IB changing the *values*, or the *numbers* that appear on the constraints?
>>
>> If a view’s frame is out of whack with its constraints, the constraints in
>> conflict will be drawn in orange, with a number badge atop them. This badge
>> represents the difference between the calculated value of that dimension and
>> the view’s current value.
>>
>> For example, if you add a horizontal centering constraint to a view, then
>> move that view 10pt to the right, the vertical centering constraint will
>> draw in orange and have a “+10” badge atop it.
>>
>> If you’re actually seeing the constraint *constants* change, then you’ve
>> certainly found a bug.
>
> Nope, it's changing constants. Even after I fix the frames, it moves them or
> changes the constraints, or something.
I'm doing the Autolayout chapter just now…
In addition to everything else, Editor > Resolve Auto Layout Issues > Add
Missing Constraints (one for the selected view, one for the whole scene, also
in the corresponding popup attached to the T-dot-T button at lower right) will
take the free-form layout you created, make its best guess at your intentions,
and add constraints to match. It's moderately intelligent — it cascades
alignments and spacing rather than giving everything an absolute position and
size — and it's good enough to proceed with development, but sooner or later,
you'll have to tune it.
— F
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
