From fnaumann@mail.cs.uni-magdeburg.de Sun Jun 27 20:59:13 2004 X-Authentication-Warning: tyrell.nvg.ntnu.no: joska owned process doing -bs Date: Sun, 27 Jun 2004 20:55:39 +0200 (CEST) From: Jo Even Skarstein X-X-Sender: joska@tyrell.nvg.ntnu.no To: MiNT Mailing List Subject: Re: [MiNT] AES desktop extension In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at fishpool.fi Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@nvg.org Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel On Sun, 27 Jun 2004, Frank Naumann wrote: > >> Invoking traps from the progdef is in general a bad idea, ... > > I only meant AES traps here. Yes, I thought so but couldn't resist ;-) Anyway, there are many good reasons to call the AES from a userdef, but the best reason is reusability - use an already existing object or tree as a part of a userdef. Example: You want to draw an icon as a part of your userdef. /* ** Jo Even Skarstein http://joska.nvg.org/ */