Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!linus!linus!mbunix.mitre.org!laf
From: laf@mbunix.mitre.org
Newsgroups: comp.sys.mac.system
Subject: Re: ResEdit 2.1 (A question to)
Message-ID: <127331@linus.mitre.org>
Date: 17 Dec 90 20:59:17 GMT
References: <6698@drutx.ATT.COM> <1990Dec2.173058.28944@santra.uucp> <1990Dec17.180900.6008@lth.se>
Sender: usenet@linus.mitre.org
Organization: The MITRE Corporation
Lines: 23

In article <1990Dec17.180900.6008@lth.se> sund@tde.lth.se (Lars Sundstr|m)
writes:
>Well, I have encountered some troubles with my copy of ResEdit 2.1:

<stuff deleted>

>+---------------------------------------------------------------------+
>| Lars Sundstrom, Lund University, Department of Applied Electronics, |
>| Box 118, S-221 00 Lund, Sweden Phone: +46-46121598 Fax:+46-46129948 |
>| Internet: sund@tde.lth.se                                           |
>+---------------------------------------------------------------------+

There's a feature (?) in that, when creating an ALRT or DLOG, instead
of a new DITL being created, the DITL of the corresponding resource
ID (if this DITL exists) is used.  For example, if there are DITL resources
128 through 135, and ALRT resources 128 and 129, creating a new ALRT will
cause the ALRT to use DITL 130, not a new DITL 136.  This is different
that the actions of the older ResEdits.  Is this a new feature?  Personally,
I dislike it, because I feel that creating a new alert implies creating
a new DITL...

Lee Fyock
laf@mbunix.mitre.org