Re: Why does IB insist on putting NSTextView in an NSScrollView
Re: Why does IB insist on putting NSTextView in an NSScrollView
- Subject: Re: Why does IB insist on putting NSTextView in an NSScrollView
- From: Ross Carter <email@hidden>
- Date: Tue, 19 Jan 2010 10:37:38 -0500
On Jan 18, 2010, at 8:54 PM, Jerry Krinock wrote:
> On 2010 Jan 17, at 14:20, Jens Alfke wrote:
>
>> On Jan 17, 2010, at 5:34 AM, Jerry Krinock wrote:
>>
>>> I don't see why an un-embedded NSTextView is not available in the Library.
>>
>> I think because it's generally considered unnecessary. Without the scrollview wrapped around it, it can't scroll, which means the amount of text it can be used with is really limited. There's not much point to that; if you want something for little bits of text, an NSTextField works better.
>
> OK. Well, I suppose I have a really odd usage then. The reason I used NSTextView instead of NSTextField is because I've got possibly several lines and need to precisely predict the layout. You can do this with NSLayoutManager for an NSTextView, but not for an NSTextField because the NSTypesetterBehavior is not reliably available.
>
> Thanks, all.
Not odd at all. There are several valid reasons for wanting a NSTextView not to be inside a NSScrollView. Any page-based view system does this (i.e., > 1 text view, all enclosed in the same scroll view). The Text System Architecture reference document illustrates some of these configurations. What is odd is that IB cannot build the configurations illustrated in the reference doc.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden