🚀 go-pugleaf

In article <23139@cup.portal.com> drew@cup.portal.com (Andrew E Wade) writes:
>I think moire 3.0 has a "hidden" feature to allow it to be interrupted (or
>not) by activity on either port (modem or printer).  Caveat:  I'm feeling
 [ description of using ResEdit to enable serial port activity deleted ]
>Again, untested.  I think i've seen interference with modem port by moire,
>before I made this change, and hope this will fix it.
>
>Why would the author hide a feature?  Good question.  Why would the default be
>off for this feature?  Certainly anyone would want any activity anywhere to
>take precedence over moire, no?

   It's certainly odd... I tried Moire 3.0 on a IIcx, and it worked without
a hitch. However, on the 512KE (which has recent 128K ROMs & new clock chip,
and is functionally equivalent to a Plus), serial port interruption is still
a problem (even after setting the appropriate field in the 'Cfig' resource).
Also, the problem with groups of lines "detaching" themselves from the moving
pattern is still present on the 512KE.

   Another problem (acknowledged in the documentation) is that Moire will
never activate if MPW is the frontmost application.

-- 
==========     .......     =============================================
Ken McLeod    :.     .:    UUCP: ...{spsd,zardoz,felix}!dhw68k!thecloud
==========   :::.. ..:::   INTERNET: thecloud@dhw68k.cts.com
                ////       =============================================