Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!zazen!news
From: gilmore@macc.wisc.edu (Neil Gilmore)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Shared IDCMP ports
Message-ID: <1991Jan13.084228.25939@macc.wisc.edu>
Date: 13 Jan 91 08:34:01 GMT
Sender: news@macc.wisc.edu (USENET News System)
Organization: University of Wisconsin Academic Computing Center
Lines: 25

In article <6841@crash.cts.com>, lkoop@pnet01.cts.com (Lamonte Koop) writes...

> 
>I'm having a problem utilizing a shared IDCMP port setup on a window
>arrangement, and wonder if anyone can see a problem with what I'm doing.
>I have one main window, and a second window is opened, after which I make
>the following assignment;

At the risk of sticking my neck out...

I also had a problem with shared IDCMP ports, even though I was 
(apparently) doing everything correctly. Your routine looked right (I 
used the one from the RKM's nearly verbatim also). My problem turned out 
to be that I was using the menu to select when to close a window, the 
window which generated the message. Unfortunatly, I was using the real 
message, not a copy, and replying at the end of an event loop. What 
would happen was the message woudl come in, I'd close the window, then 
Reply() to the message. Of course, by the time I'd Reply(), the window 
didn't exist, or maybe the message I was Replying to was alredy Replyed 
to. In any case, a quick trip to the guru. The problem wasn't in closing 
the window, but what went on around closing the window. Now, I copy the 
message and Reply() immediately, and haven't crashed since on closing a 
window.

Hope this helps.