Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!uunet!intercon!news
From: amanda@mermaid.intercon.com (Amanda Walker)
Newsgroups: comp.sys.mac.programmer
Subject: Re: I hate it when Apple does this . . .
Message-ID: <1990Mar13.000006.13766@intercon.com>
Date: 13 Mar 90 00:00:06 GMT
References: <420@fornax.UUCP> <88@ndcvb.cc.nd.edu> <422@fornax.UUCP> <7133@goofy.Apple.COM>
Sender: gaige@intercon.com (Gaige B. Paulsen)
Reply-To: amanda@mermaid.intercon.com (Amanda Walker)
Organization: InterCon Systems Corporation, Sterling, VA
Lines: 21

In article <7133@goofy.Apple.COM>, chewy@apple.com (Paul Snively) writes:
> As I recall, the reason that we have Set/GetIText is that there's some 
> additional information about text being maintained by the Dialog Manager, 
> such that you can't simply munge the text handle and expect the right 
> things to happen.

I've never had any problem doing all sorts of violence to dialogs behind
the DM's back (hmm.. no pun intended there :-)).  SetIText and GetIText
make it real easy to move things between text fields (of either flavor)
and Str225's.  However, GetDItem and SetDItem seem to handle all of the
actual bookkeeping and keeping TextEdit informed as to what's going on.

I use GetDItem and SetDItem to avoid the 256-character-per-field limitation
you get with GetIText & SetIText.

--
Amanda Walker
InterCon Systems Corporation

"Many of the truths we cling to depend greatly upon our own point of view."
	--Obi-Wan Kenobi in "Return of the Jedi"