On 12/11/2010, at 12:45 AM, Eric Gorr wrote:
> It seems to me that NSTextView can do everything that NSTextField can and
> more. For example, on a NSTextView, one can use the method
> setHorizontallyResizable: and then call sizeToFit to get it to resize itself
> vertically instead of horizonta
t; From: Erik Buck
>> Subject: Re: NSTextView vs NSTextField
>> To: "Cocoa Dev" , "Eric Gorr"
>>
>> Date: Thursday, November 11, 2010, 10:50 AM
>> NSTextField doesn't display or edit
>> text at all. It uses an instance of NSTextView call
Change Filed to Field where appropriate. Grumble...auto-correct...grumble.
--- On Thu, 11/11/10, Erik Buck wrote:
> From: Erik Buck
> Subject: Re: NSTextView vs NSTextField
> To: "Cocoa Dev" , "Eric Gorr"
>
> Date: Thursday, November 11, 2010, 10:50 AM
&g
hole text infrastructure for every label and leave
it set up...the best answer is that all of this software worked well on 8MB
NeXT Cubes, and not instantiating the entire text system for every field is one
reason why.
--- On Thu, 11/11/10, Eric Gorr wrote:
> From: Eric Gorr
> Subj
> If so and if I am programmatically creating one of these controls, is there
> any reason why I would want to use a NSTextField?
> (I know that IB uses a NSTextField for Labels, for example...is this just a
> historical artifact?)
For editing multiple strings it is more efficient to have multip
It seems to me that NSTextView can do everything that NSTextField can and more.
For example, on a NSTextView, one can use the method setHorizontallyResizable:
and then call sizeToFit to get it to resize itself vertically instead of
horizontally.
Is this correct?
If so and if I am programmatica
