🚀 go-pugleaf

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.
> [...] 
>Now, the problem comes when I try to close the second window.  NOw, 
>I realize you cannot simply do this normally, so I use the following
>routine:
> 
>void SafeClose(swin)
>struct Window *swin;
>{
>    struct IntuiMessage *msg;
>    struct IntuiMessage *succ;
>    struct MsgPort      *mp = (struct MsgPort *)swin->UserPort;
> 
>    Forbid();
>    msg = (struct IntuiMessage *)mp->mp_MsgList.lh_Head;
>    while(succ=(struct IntuiMessage *)msg->ExecMessage.mn_Node.ln_Succ) {
>        if (msg->IDCMPWindow == swin) {
>           Remove(msg);
>           ReplyMsg(msg);
>        }
>        msg = succ;
>    }
>    swin->UserPort = NULL;
>    Permit();
>    CloseWindow(swin);
>}
>
>Generally, calling this results in a corrupt memory list guru. Now, anyone
>have a suggestion?  I realize this is an old topic, but I cannot find
>referernces to it presently.  
>

Try adding 

     ModifyIDCMP(swin,0L);

between the Permit() and the CloseWindow() calls. It's the only
difference between yours and the one that I have (that works.)

bj

 -----------------------------------------------------------------------
 | Brian Jackson  Software Engineer, Commodore-Amiga Inc.  GEnie: B.J. |
 | bj@cbmvax.cbm.commodore.com    or  ...{uunet|rutgers}!cbmvax!bj     |
 | "My beer comes from farther away than your beer."                   |
 -----------------------------------------------------------------------

 ** Error Correction **

In article <17379@cbmvax.commodore.com> bj@cbmvax.commodore.com (Brian Jackson) writes:
>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.
>> [...] 
>>Now, the problem comes when I try to close the second window.  NOw, 
>>I realize you cannot simply do this normally, so I use the following
>>routine:
>> 
   [ some example code deleted ] 

>>    swin->UserPort = NULL;
>>    Permit();
>>    CloseWindow(swin);
>>}
>
>Try adding 
>
>     ModifyIDCMP(swin,0L);
>
>between the Permit() and the CloseWindow() calls. It's the only
>difference between yours and the one that I have (that works.)
>
>bj
 
Argh!!  Try adding it BEFORE the Permit() call!  My mistake (the excuse is
my staying up all night playing with computers).  Thanks to Peter!!

 -----------------------------------------------------------------------
 | Brian Jackson  Software Engineer, Commodore-Amiga Inc.  GEnie: B.J. |
 | bj@cbmvax.cbm.commodore.com    or  ...{uunet|rutgers}!cbmvax!bj     |
 | "It can be done." != "It should be done."                           |
 -----------------------------------------------------------------------

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;
> 
>secondwin->UserPort = firstwindow->UserPort;

	This is besides the point in question but aren't you wasting
  memory here?  Your UserPort is unlinked here and you haven't bothered
  to restore it when you close the window.  (from the Code below)
  Assuming Intuition allocates UserPort rather than just give you a
  pointer to an existing port.

>void SafeClose(swin)
>struct Window *swin;
>{
>    struct IntuiMessage *msg;
>    struct IntuiMessage *succ;
>    struct MsgPort      *mp = (struct MsgPort *)swin->UserPort;
> 
>    Forbid();
>    msg = (struct IntuiMessage *)mp->mp_MsgList.lh_Head;
>    while(succ=(struct IntuiMessage *)msg->ExecMessage.mn_Node.ln_Succ) {
>        if (msg->IDCMPWindow == swin) {
>           Remove(msg);
>           ReplyMsg(msg);
>        }
>        msg = succ;
>    }
>    swin->UserPort = NULL;
>    Permit();
>    CloseWindow(swin);
>}
>
>Generally, calling this results in a corrupt memory list guru. Now, anyone
>have a suggestion?  I realize this is an old topic, but I cannot find
>referernces to it presently.  
>
>
>                             LaMonte Koop
> Internet: lkoop@pnet01.cts.com         ARPA: crash!pnet01!lkoop@nosc.mil
>           UUCP: {hplabs!hp-sdd ucsd nosc}!crash!pnet01!lkoop
>  A scientist is one who finds interest in the kinetic energy of Jell-O
>   moving at ridiculous velocities...an engineer is one who can find a
>               real-life application for such silliness.


___________________________________________________________________________
    //	"Be Excellent to Eachother"   - Bill & Ted
\\ //	"And Most of All Be Excellent to Your Amiga"
 \X/				      - Will   wsc1@cunixb.columbia.edu
___________________________________________________________________________