🚀 go-pugleaf

Dear MacApp'ers --
 
Regarding my accompanying link ("TEditText Bug")...
 
I would speculate that this is a bug whose fix will:
 
(a) involve a very slight change to the MacApp code;
(b) easily be seen to not have distant side-effects;
(c) at best show up in an Apple bug doc, and that only if we're unexpectedly
lucky (Kent says he's being transfered to another engineering department!);
(d) belong in MacApp 3.0.2 (which there is no indication we will ever see Apple
create or distribute).
 
If Apple supported MacApp 3.0, then this is what would happen now:
(1) Apple confirms and repairs this very small and easy bug.
(2) The fix is made to MacApp 3.0.2, which is distributed on ETO #10.
 
Since Apple no longer supports MacApp 3.0 [Go ahead: prove me wrong! Follow
the above 2 steps.], let us suppose that MADA buys it. Then here is the
scenario:
 
(1) I, or someone else, figures out the fix and posts it here. One or two other
active MacApp'ers who could be personally affected by this bug check to confirm
that the fix looks right to them.
 
(2) MADA's hired, full-time (if necessary) MacApp maintainer examines the
proposed fix, and if all still agree that it looks okay, makes the change to
the MADA master copy of MacApp.
 
(3a) The revised MADA master is distributed on the next quarterly MADA MacApp
CD-ROM, to which those of us who are actively using MacApp have subscribed.
 
-or-
 
(3b) The revised MADA master is distributed on Apple's ETO #10. (Apple paying
part of our ETO subscription price [the part previously going to support MacApp
support] to MADA as a licensing fee.)
 
 
-- Dave Goldman
   Research Software Design