Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!mcsun!ukc!edcastle!helium!gordonc
From: gordonc@aifh.ed.ac.uk (Gordon Cameron (RA DAI))
Newsgroups: comp.windows.x
Subject: Re: NOTIFY Dispatch WOES!
Message-ID: <1991Jun21.150110.9991@aifh.ed.ac.uk>
Date: 21 Jun 91 15:01:10 GMT
References: <9106191549.AA25895@genmri.sane.COM>
Organization: Dept AI, Edinburgh University, Scotland
Lines: 32

From article <9106191549.AA25895@genmri.sane.COM>, by mms@genmri.UUCP (Mark Scoville):

mms@genmri.UUCP (Mark Scoville):
> I am attempting EXPLICIT DISPATCHING, and am failing sorely!  After invoking
> the application, I toggle back and forth about 3 times or so between 'Start
> Loop' and 'STOP'.  At some point it hangs on STOP.

I find that explicit dispatching seems to work some of the time, and not at
other times. It seems that you have to watch that you are doing your
dispatching before you clear the input buffer. If you have a fast loop that
issues a dispatch, but does a colurmap flush, or screen update or something
in between dispatches, then the whole thing seems to fall down, and the
notifier hangs completely.

The solution for me is that I now use XView timers. When an event occurs and
I want to start doing something which I might want to abort, I start a
timer, and the bit of code going. Now I don't have to worry about stopping
and starting the notifier, as my timer function simply checks to see if a
flag has been set by pressing a button. If so, then the timer stops, and
your application aborts. 	

( See timers section in O`Reilly, Volume 7 )

I reckon explicit dispatching just does not work properly.

Hope this is helpful,

Gordon Cameron/ Andrew Fitzgibbon,
Dept. of AI,
Edinburgh University.

e-mail : gordonc@uk.ac.ed.aifh