Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!think!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!kit
From: kit@EXPO.LCS.MIT.EDU (Chris D. Peterson)
Newsgroups: comp.windows.x
Subject: Re: Need help deriving new widget from list widget
Message-ID: <9003051844.AA23173@expo.lcs.mit.edu>
Date: 5 Mar 90 18:44:03 GMT
References: <TOM.90Mar3163037@hcx2.ssd.csd.harris.com>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 24


> If I try to write an initialize() procedure for my widget, it gets called
> after the List widget has already had its initialize procedure called. But
> the List widget is the one that needs to do the initialization after I
> provide the list. If I try and use the XtListChange() procedure from within
> my initialize procedure it dies because it only seems to work right if the
> widget is already realized, but it certainly has not been realized since I
> am still in the initialization stage.

1) You could always call the List widget's initialization procedure again.

2) You could just perform the initialization stuff by rewriting that code w/o
   rewriting the entire list widget.

I believe that the problems with XawListChange(XtListChange in R3) have been
solved, but don't remember for sure.


						Chris D. Peterson     
						MIT X Consortium 

Net:	 kit@expo.lcs.mit.edu
Phone:   (617) 253 - 9608	
Address: MIT - Room NE43-213