On Aug 23, 2013, at 3:22 PM, Jerry Krinock wrote: > On 2013 Aug 23, at 12:53, Ken Thomases <k...@codeweavers.com> wrote: > >> I think it's just that, if you use -setContentMinSize:, you shouldn't also >> use -setMinSize:. > > Yes, I'd thought of that, and checked for it with the Find Navigator, but the > answer is that I was *not* using setContentMinSize: anywhere on this window. > Just rechecked. Same answer.
Is the window from a NIB? Does it have a min size (content or frame) set there? >> "This method takes precedence over setMinSize:." > > Indeed, but the phrase "takes precedence" leaves some loose ends. For > example, if a setter method gets "precended over" :)), does its ivar get set > and ignored, or does the method become a no-op? "ivar"? What is this "ivar" you speak of? Sounds like an imaginary implementation detail of which you have (and should have) no knowledge. It is, however, an open question as to how the visible behavior of the property, as seen through its getter, is affected. I suppose that could use some clarification. Regards, Ken _______________________________________________ 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
