Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!elroy!cit-vax!ucla-cs!zen!ucbvax!latlog.UUCP!PAYNE
From: PAYNE@latlog.UUCP
Newsgroups: comp.windows.x
Subject: X toolkit
Message-ID: <494.8711171145@latlog.co.uk>
Date: Tue, 17-Nov-87 06:45:40 EST
Article-I.D.: latlog.494.8711171145
Posted: Tue Nov 17 06:45:40 1987
Date-Received: Thu, 19-Nov-87 23:20:52 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 29

I have been using the X toolkit for some time now and have got to the
point where I want to be able to have multiple instances as children
of the root window (not the toplevel widget). I missed most of the earlier
discussion on the toplevel widget so I hope someone will be kind enough to
explain the situation again. In the belief that I could not do this given
the current toplevel implementation I have created a root window widget
which does nothing but whose id I can pass through to other widgets as
their parent (exactly as you would do for windows). Is this the correct
approach or will I run into problems at some point?
Incidentally I am currently getting warnings telling me that the widget
is not managed in XtGeometryRequest, I haven't yet discovered if this
refers to the parent (i.e. my root widget) or the child widget.

Is it possible for the toolkit team to put out an `approved' fix for this
problem to save us hacking up our own, or alternatively please tell me where
I am going wrong if what I want to do is already possible?

I have another releated question, I am using a SUN 3/110 so I have access
to two screens. I would like to explore the possibility of writing to the
two screens from within one application, can I do this using the toolkit
as it currently stands?

Related to this is a question for the window manager people, why do I have
to run a uwm for EACH screen, surely one uwm could deal with all screens,
after all thats what the X server does?

Thanks, Julian Payne.
European Silicon Structures (ES2).
(payne@latlog.uucp)