🚀 go-pugleaf

In article <14990@cbmvax.commodore.com> peter@cbmvax.commodore.com (Peter Cherna) writes:
>In article <1783@shodha.enet.dec.com> ridder@elvira.enet.dec.com (Hans Ridder) writes:
>>In article <14939@cbmvax.commodore.com> jesup@cbmvax.commodore.com (Randell Jesup) writes:
>>>	This has been fixed.  Don't worry, in the later versions of 2.02 beta
>>>the problem was fixed, and it works as it did in 1.3.
>>                                     ^^^^^^^^^^^^^^^^
>>You mean it's back to clearing out the "menu bar" area on on screens
>>opened with the CUSTOMBITMAP and SCREENQUIET flags?
>
>No.  Things work AS THEY SHOULD, meaning that SCREENQUIET is
>truly quiet (true for 2.0 and up) and CUSTOMBITMAP works fine
>(it did in 1.3, 2.00, 2.01, and 2.02, and ...).

Glad to hear that these things work AS THEY SHOULD.  The SCREENQUIET
"problem" isn't noticed unless you use it with CUSTOMBITMAP, so I
referred to them together.  I wasn't trying to say that CUSTOMBITMAP was
broken.

>Raising alarm over the performance of beta software is inappropriate,
>in my opinion.  Problems should be sent c/o your favorite engineer,
>or better yet, to

Sorry if you took offense, Peter, and sorry you got the impression that
I was "raising an alarm".

The original poster said that instead of just clearing the "menu bar"
area as 1.3 did, some version of 2.0 was clearing the entire screen
(bitmap, actually).  Randell Jesup then said that it had been fixed, and
to quote: "it works as it did in 1.3."  (Look up there, "it's in there!")

I was merely trying to clarify if Commodore thought that clearing the
"menu bar" area (in 1.3) was a "feature", and would be carried into the
final release of 2.0.

It was just a question.

>     Peter

-hans
------------------------------------------------------------------------
  Hans-Gabriel Ridder			Digital Equipment Corporation
  ridder@elvira.enet.dec.com		Customer Support Center
  ...decwrl!elvira.enet!ridder		Colorado Springs, CO