Re: NSView resizing problems.
Re: NSView resizing problems.
- Subject: Re: NSView resizing problems.
- From: Geoffrey Holden <email@hidden>
- Date: Mon, 20 Sep 2010 16:31:56 +0100
You make an excellent point. But you raise two questions.
1. If '' isn't the correct way to initialize, what is?
2. Should I just create an arbitrary placeholder framesize and use that
during initialization? Or is it acceptable to set no framesize at all at
this stage?
Thanks for your help.
On Mon, Sep 20, 2010 at 3:52 PM, Keary Suska <email@hidden>wrote:
> On Sep 20, 2010, at 5:45 AM, Geoffrey Holden wrote:
>
> > My problem is that when I load this view into a tab (using the attached
> > code), the textview doesn't fit on the screen. It covers up the top
> > textfield and seems to have it's top edge somewhere above the tabview (as
> > follows)
>
> The most common reason for this is that you are shrinking the view such
> that it forces the subviews to overlap, which creates an undefined situation
> that the view cannot handle.
>
> > Messenger* messenger = [[Messenger alloc] initWithApp:@"Messenger"
> > :self];
> > [currentConversations setObject:messenger forKey:[NSNumber
> > numberWithInt:convId]];
>
> And here is where you are doing it:
>
> > NSView* newView = [[[NSView alloc] init] autorelease];
>
> This is not the designated initializer. Don't do this.
>
> > [newView setAutoresizesSubviews:YES];
> > [[messenger view] setFrame:[newView frame]];
>
> Why do you expect [newView frame] to return a sensible value?
>
> HTH,
>
> Keary Suska
> Esoteritech, Inc.
> "Demystifying technology for your home or business"
>
>
_______________________________________________
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