Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!aplcen!haven!udel!rochester!pt.cs.cmu.edu!o.gp.cs.cmu.edu!cs.cmu.edu!Eric.Thayer
From: Eric.Thayer@cs.cmu.edu (Eric H. Thayer)
Newsgroups: comp.sys.next
Subject: Re: cthreads and modals
Message-ID: <1990Sep23.234815.16555@cs.cmu.edu>
Date: 23 Sep 90 23:48:15 GMT
References: <9009220547.AA16749@nextasy2.eecs.wsu.edu>
Sender: netnews@cs.cmu.edu (USENET News Group Software)
Organization: Carnegie Mellon School of Comp. Sci.
Lines: 22


In article <9009220547.AA16749@nextasy2.eecs.wsu.edu> 
dwatola@NEXTASY2.EECS.WSU.EDU writes:
> This program works fine if I remove the NXRunAlertPanel() call.  So my 
question
> is, is there some reason why the modal alert panel should not work from 
an
> inferior thread?  Anyone out there got any ideas or educated guesses?

The NeXTStep expects that all display updates will be a result of some 
event.  So, if you go an generate a display update outside of the 
processing of an event, things tend to go haywire in a hurry.   One way to 
approach this problem is to create a new speaker object and connect it to 
the applications listener.  You can then implement an remote method  which 
brings up an alert panel.  It's a little perverse, but up to this point, I 
have not seen a good solution to the problem.

Hope this helps

----------------------------------
Replies can have NeXT attachments in them
Phone: (412)268-7679