Path: utzoo!attcan!utgpu!watmath!cantuar!greg
From: greg@cantuar.UUCP (G. Ewing)
Newsgroups: comp.windows.news
Subject: Re: Help required with damaged events
Keywords: Damaged Events, Repair of Canvases etc
Message-ID: <1079@cantuar.UUCP>
Date: 17 Apr 89 03:26:41 GMT
References: <2726@crete.cs.glasgow.ac.uk>
Reply-To: greg@cantuar.UUCP (G. Ewing)
Organization: University of Canterbury, Christchurch, New Zealand
Lines: 21

Catherine Anne Wood (cathy@cs.glasgow.ac.uk) writes:
>RepairDamage (at the moment) just prints out a message on the console to
>say it has been called .. this never happens.

I had a similar problem once.

If the repair routine never calls damagepath, then the after the first
damage event, NeWS won't give you any more, since it thinks you
haven't got the first one yet. damagepath clears the accumulated
damage path, allowing further damage events to occur.

The repairing code should look something like:

	damagepath clipcanvas
	% draw your stuff
	newpath clipcanvas

Greg Ewing				Internet: greg@cantuar.uucp
Spearnet: greg@nz.ac.cantuar		Telecom: +64 3 667 001 x8357
UUCP:	  ...!{watmath,munnari,mcvax,vuwcomp}!cantuar!greg
Post:	  Computer Science Dept, Univ. of Canterbury, Christchurch, New Zealand
Disclaimer: The presence of this disclaimer in no way implies any disclaimer.