Re: More constraints confusion
Re: More constraints confusion
- Subject: Re: More constraints confusion
- From: Rick Mann <email@hidden>
- Date: Thu, 25 Apr 2013 16:50:00 -0700
No, pinning is not what I want. That's what I'm trying to avoid. IB in insisting on pinning the width and the height.
I think it assumes the NSImageWell MUST have a static size, rather than allow it to resize. I'm able to put an NSView without this problem.
On Apr 25, 2013, at 16:48 , Caylan Larson <email@hidden> wrote:
> Rick,
>
> Search the help menu for "pin" and see if pinning the height or width gets you to where you need to be.
>
> Caylan
>
> On Apr 25, 2013, at 6:39 PM, Rick Mann <email@hidden> wrote:
>
>> I put an NSImageView into a window. I want the NSImageView's frame to always fill the window content frame.
>>
>> When I dropped it in, IB gave it a width and height constraint that I can't edit. I sized it to fit the window, and it also added leading and trailing space constraints.
>>
>> I explicitly set top and bottom constraints.
>>
>> But the width & height constraints can't be edited. If I promote them to user constraints, and then try to delete them, they just come back.
>>
>> Why does IB think they are necessary?
>>
>> --
>> Rick
>>
>>
>>
>>
>> _______________________________________________
>>
>> Cocoa-dev mailing list (email@hidden)
>>
>> 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:
>>
>> This email sent to email@hidden
--
Rick
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden