Xref: utzoo comp.windows.x:34834 comp.windows.x.motif:2419
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!mcsun!ukc!stc!stl!siesoft!paulb
From: paulb@siesoft.co.uk (Paul Bentley)
Newsgroups: comp.windows.x,comp.windows.x.motif
Subject: Re: Secondary Loop (within XtMainLoop) Problems
Message-ID: <1991Apr3.092416.8894@siesoft.co.uk>
Date: 3 Apr 91 09:24:16 GMT
References: <1991Apr2.080151.10992@neon.Stanford.EDU>
Sender: usenet@siesoft.co.uk (NNTP Poster)
Organization: Siemens System Developement Group, Reading, UK.
Lines: 27


I have also experienced considerable difficulty in making subsiduary
event loops work in Motif 1.1 and have spent several days producing short
(50 lines approx.) example programs. The manifestation of these problems
are in my experience always obscure, so obscure infact that you have to
spend a lot of time convincing yourself that you have not made the mistake
in your own code.

My opinion is that any problem caused by the use of subsiduary event loops
is a bug. I have never seen anything in writing to say that they are not
allowed, and the bugs that appear are just too obscure to be features.

However I do accept the point of view that subsiduary event loops should be
avoided. My advice would be not to write any new applications using subsiduary
event loops. I'm in the unfortunate position of maintaining old code ported
to Motif (far from ideal) which has blocking subsiduary event loops called
from 70 places !

--------------------------------------------------------------------------------

Paul Bentley (paulb@siesoft.co.uk)
Siemens Nixdorf
Informations Systems Limited
Siemens Nixdorf House
Oldbury, Bracknell
Berkshire RG12 4FZ
England.