Path: utzoo!attcan!ncrcan!becker!censor!comspec!tvcent!lethe!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!samsung!munnari.oz.au!metro!bunyip!moondance!focl5!thyssen
From: thyssen@focl5.cs.uq.oz.au (Anthony Thyssen)
Newsgroups: comp.sys.amiga
Subject: Re: Problem with CreateProc & LoadSeg
Message-ID: <3504@moondance.cs.uq.oz.au>
Date: 7 May 90 03:02:23 GMT
References: <897@tau.sm.luth.se>
Sender: news@moondance.cs.uq.oz.au
Reply-To: thyssen@focl5.cs.uq.oz.au (Anthony Thyssen)
Organization: Dept of Computer Science, Iniversity of Qld, Australia
Lines: 14


|	signalmask=1L << win->UserPort->mp_SigBit;
|	
|	while (!done){    /* Wait until closegadget is selected */
|		signals=Wait(signalmask);
|		if (signals & signalmask);
|			done=handleIDCMP(win);	
|		};

    Arrrrggghhhh.....  Would ALL programers out there please include
the BREAK_C signal flags in their code for testing for the close gadget
It not only allow the user the send a break for easier testing but is a good
thing to do..  To many programs Especially those for CLI don't do this
Programers who leave it out should be shot.