Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!ATHENA.MIT.EDU!kit
From: kit@ATHENA.MIT.EDU (Chris D. Peterson)
Newsgroups: comp.windows.x
Subject: Re: Multiple independant widgets
Message-ID: <8901261905.AA02938@DORA.MIT.EDU>
Date: 26 Jan 89 19:05:14 GMT
References: <5799@phoenix.Princeton.EDU>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 37


> I was trying to create two semi-independent widgets in the same application 
> and I did what seemed to be the obvious thing -- I created two widgets
> under toplevel, one of type compositeWidgetClass and the other 
> asciiStringWidgetClass -- and it didn't work. 

All current shell widgets only know how to MANAGE one child.  If you give
them more than that they get confused and do the wrong thing.
It is possible to have many children in a shell widget, but at most one
can be managed.  This means that the application must handle all other 
geometry management.  This is usually more of a pain than it is worth 
though, and I suggest that you think twice before doing it, but it is possible.

The other possibility is to have only one of your widgets managed at a time,
so when you want the text widget visable then you unmanage the other composite
widget and manage the text wiget.  This assures that the shell widget has only
one child to manage, and it knows how to do this.

> Also, it is ignoring the XtNx and XtNy fields in the ArgLists.  

Remember that it is the parent who has the final decision where its children
widgets will be placed, so that all parent widgets are allowed to ignore the 
XtNy and XtNx positions supplied by their children.

> Thanks in advance.

Your welcome :-)

						Chris D. Peterson     
						MIT X Consortium /
						Project Athena 

Net:	kit@athena.mit.edu		
Phone: (617) 253 - 1326			
USMail: MIT - Room E40-321
	77 Massachusetts Ave.		
	Cambridge, MA 02139