Re: Autolayout frustrations with NSOutlineView
Re: Autolayout frustrations with NSOutlineView
- Subject: Re: Autolayout frustrations with NSOutlineView
- From: Roland King <email@hidden>
- Date: Wed, 30 Jul 2014 09:30:44 +0800
>
> One of the things I'm a bit unclear on is the 'content compression resistance priority' of the outline view, which I've set to be a lowish number (90), my thinking being that I want it to compress readily, so this value should be 'weak'. Or does that imply this should be a high number to ensure that the compression is allowed as a priority? The documentation doesn't really help me understand this. Anyway, changing this value has no effect on the result, so it may be a red herring.
>
Can’t say much about the rest, but compression resistance, the hint’s in the name, it’s how strongly something resists being compressed narrower than its intrinsic content size width.
Content compression resistance is really just a constraint which says
width >= intrinsic content width
just as content hugging is just
width <= intrinsic content width
In general having something smaller than intrinsic width is bad because it cuts off the content, but having it required (priority 1000) to be >= intrinsic width is also bad when you just don’t have the room, hence the content compression priority is lower than ‘required', but higher than the hugging one, so a view gets a bit wider than it really wants before it gets a bit narrower than it wants in the case it can’t be exactly the size it wants.
Anyway an outline view sounds like something which doesn’t want constraints on it bar those installed by its owner and it probably doesn’t have an intrinsic content width anyway so compression resistance is probably futile.
_______________________________________________
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