Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!samsung!noose.ecn.purdue.edu!news
From: moyman@ecn.purdue.edu
Newsgroups: comp.sys.mac.programmer
Subject: LSC 4.0 cdev and editText items!!
Message-ID: <1990Dec14.213435.9514@noose.ecn.purdue.edu>
Date: 14 Dec 90 21:34:35 GMT
Sender: news@noose.ecn.purdue.edu (USENET news)
Reply-To: moyman@ecn.purdue.edu
Organization: Engineering Computer Network
Lines: 34

What's the deal with textEdit items inside the cdev dialog!! TextEdit acts
*real wierd on these items... Reading in strings ('STR ' resource ) and setting
them to editText (boxes) items results in the first item (SysTextID) to be
invisible (it's is there, you just can't see it), the rest come out correctly.
But clicking inside the editText box (the first, the invisible one) does
nothing, only until you click inside one of the other editText boxes does it
become *active*. All of the edit boxes act *weird*... I do something like the
following (at init time of the cdev) to set the initial values of my 4 editText
boxes...

	/* Setting the initial text in all of the editable text fields */
	aStr = GetString(SysStrID);
	GetDItem(dp,lastItem+SysTextID,&itemType,&itemHandle,&itemRect);
	SetIText( itemHandle, *aStr);
	
	aStr = GetString(ClosedStrID);
	GetDItem(dp,lastItem+ClosedTextID,&itemType,&itemHandle,&itemRect);
	SetIText( itemHandle, *aStr);
	
	aStr = GetString(OpenStrID);
	GetDItem(dp,lastItem+OpenTextID,&itemType,&itemHandle,&itemRect);
	SetIText( itemHandle, *aStr);
	
	aStr = GetString(ChooserStrID);
	GetDItem(dp,lastItem+ChooserTextID,&itemType,&itemHandle,&itemRect);
	SetIText( itemHandle, *aStr);

Anybody know what the deal is...Am I not able to treat/code (the items) the
cdev dialog like a *regular* dialog??... All of my other titem seem to work
perfectly fine... I am using LSC 4.0...

Mike Moya
Engineering Computer Network
Purdue University