Re: NSWindow setMinSize: jumps up to current size instead
Re: NSWindow setMinSize: jumps up to current size instead
- Subject: Re: NSWindow setMinSize: jumps up to current size instead
- From: Jerry Krinock <email@hidden>
- Date: Fri, 23 Aug 2013 13:22:47 -0700
On 2013 Aug 23, at 12:53, Ken Thomases <email@hidden> 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.
> "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?
> Really? You don't see -setFrameFromString:, -setFrameOrigin:, etc.?
Ah, I didn't read the fine print. I'd assumed that setFrame would be followed by a colon. You are correct.
> I think the failure of -setMinSize: to do what you expect is explained by you also using -setContentMinSize:.
No, I wasn't. But anyhow, I've switched to using -setContentMinSize: now, and all is good and I'm on to my next issue :)
Thanks as usual, Ken.
_______________________________________________
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