Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!mit-eddie!bloom-beacon!eru!hagbard!sunic!mcsun!unido!pcsbst!aida!horst
From: horst@aida.pcs.com (horst kern)
Newsgroups: comp.windows.x.motif
Subject: Re: cursor fonts
Message-ID: <1019@pcsbst.pcs.com>
Date: 27 Nov 90 11:23:18 GMT
References: <1003@pcsbst.pcs.com> <3206@exodus.Eng.Sun.COM>
Sender: news@pcsbst.pcs.com
Reply-To: horst@aida.pcs.com (horst kern)
Organization: PCS Computer Systeme GmbH
Lines: 47

In article <3206@exodus.Eng.Sun.COM> argv@turnpike.Eng.Sun.COM (Dan Heller) writes:
>In article <1003@pcsbst.pcs.com> horst@aida.pcs.com (horst kern) writes:
>> There was a recent posting asking how to change the cursor font to the 
>> watch cursor. 
>
>Recent?

Okay, everything is relative. Recent was meant to be based on Bavarian 
time units. 

>I've found that the easiest thing to do (so far) is to create a
>single InputOnly window (you can use XCreateWindow() for this) that
>goes over the entire screen (DefaultWidget() and DefaultHeight())

The problem seems to grow instead of being solved. Some e-mail from
Mike Websters (my thanks to him) told me to map the InputOnly window
on top of the one that I want it. You think it should be the whole
screen. As you mention, it's an easy way - so far. It's of course not
the best way, as people might have windows to other machines which are 
not at all affected by the absence of one particular main loop. Even
on one machine they might want to continue with another xterm while
that machine is also busy with an application. 

So the question comes to: "How do I determine which windows are on the 
screen that are children of my main program." It can surely be solved, 
but is not so easy to do. 

I even heard of the possibility to have several main loops in one
application, using several application contexts. However I _do_ use
several application contexts and do not have the impression that a
busy window of one context leaves the window of the other context
ready to process input. 

The problem needs a solution. Leaving and entering a busy (sub-)window
several times in a focus-on-enter environment makes the mwm so
angry that it goes on strike until the busy application is killed.

Regards,
 Horst

==========
Horst Kern                                     PCS Computer Systeme GmbH
Tel.       :      089/68004-279                Pfaelzer-Wald-Str. 36
DOMAIN     :      horst@aida.pcs.com           D 8000 Muenchen 90
UUCP-Europe:      ...unido!pcsbst!horst
UUCP-USA   :      ...pyramid!pcsbst!hk
------------------------------------------------------------------------