Path: utzoo!attcan!uunet!ginosko!gem.mps.ohio-state.edu!csd4.csd.uwm.edu!mailrus!cwjcc!gatech!hubcap!mikeoro
From: mikeoro@hubcap.clemson.edu (Michael K O'Rourke)
Newsgroups: comp.sys.mac.programmer
Subject: Notification Manager question
Message-ID: <6293@hubcap.clemson.edu>
Date: 20 Aug 89 17:33:26 GMT
Organization: Clemson University, Clemson, SC
Lines: 25

I have, i hope, a simple question about the notification manager.  I have a
appletalk program which may receive packets while in the background.  One
of the options is to use the NM to tell the user when a packet is received
when in such a case. if more than one packet is received, then it only
queues up a NM task upon the first receive while in the background.

My question is this:
Is it all right to queue up a NM task (one that blinks icon, beeps, and 
places mark in apple menu) and yet have the program continue to run 
until the user chooses to bring to foreground? Right now, when it gets its
first packet while in background, it queues up NM task fine.  But when it get
the next packet in background it either locks or the program comes to
foreground for a second and then goes back the background.  This does NOT
happen if i turn the Not. Man. option off.  There may be a bug in my NM code,
but i think it is all right. (I made it from example code i have that works, 
including the TN code from Apple).

Anybody had a similiar experience.  Am i violating the purpose of the NM by  
letting the program continue to run without forcing the user to bring the 
app to foreground before it continues?


Thanx,

Michael O'Rourke