Re: Why does setFrame: change the origin of the bounds?
Re: Why does setFrame: change the origin of the bounds?
- Subject: Re: Why does setFrame: change the origin of the bounds?
- From: James Bucanek <email@hidden>
- Date: Fri, 12 May 2006 10:49:53 -0700
James Bucanek wrote on Friday, May 12, 2006:
>Shouldn't the relative origin of the bounds of an NSView remain the same at
>all times? Shouldn't a subview at {10,20} stay at {10,20} regardless of what
>happens to the frame of that NSView?
>
>- I was wondering if the autoresize flags were getting me. I set them to every
>possible combination of vertical resize flags and it made no difference.
Not two minutes after I pressed the send button, I found the problem. It wasn't the autoresize flags of the NSBox that was messing me up; it was the autoresize flags of the individual subviews themselves. When I change the NSBox's frame, it dutifully resized the subviews which were anchored to the top edge of their superview. Turning off all vertical autoresize flags solved the problem.
Sorry for the interruption.
--
James Bucanek
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden