John Small wrote:
> ** Reply to message from WD Loughman <wdloughman@xxxxxxxxxxxxx> on Mon, 01 May
> 2006 02:11:30 -0700
[ snip ]
>>Did you receive the following?
[ snip ]
> Yes, I did. But I'm sorry to admit that it got overlooked until I saw this
> message.
>
> The new beta I uploaded today should fix "A" & "B". The problem was that 4OS2
It does eliminate the "A-B" problem.
> apparently displays a message when a file is deleted. CMD.EXE does not.
>
>
>>IMPORTANTLY, in "C" the blue demonstrates screen areas *not blanked* by
>>your WU-monitor -- causing the problem shown in "B".
[ snip ]
> "C" occurs when the background color is something other than the default
> (black). Fixing "C" may take a while. In fact I may not be able to fix it
> and
> therefore I would have to abandon the color for the messages displayed
> occasionally at the bottom of the screen.
>
> As a temporary fix (which disables the color), you can do the following:
> Lines 834-835 should read:
> cfg.ansi = (CheckAnsi() == 1)
> if cfg.ansi == 1 then
> Insert a line between them so that they are:
> cfg.ansi = (CheckAnsi() == 1)
> cfg.ansi = 0
> if cfg.ansi == 1 then
>
> Let me know how this works for you.
That works fine too.
BUT... Another problem is back:
Invoking the beta monitor from a CLI works just like from a desktop
object. EXCEPT: when closing the monitor window, the entire CLI window
goes away too.
This was a problem with one of the original builds. I wrote you about
it it back then, and you fixed it. Broken again, it seems.
A real pain to (re)open a new CLI, then drill down again through eight
or so sub-dirs to get back where I was. ;)
* * * *
Thanks!!! for all your work on the monitor generally.
Double-Thanks!!! for your attention to these little oddities.
- Regards, Bill
--
WD "Bill" Loughman - Berkeley, California USA
http://home.earthlink.net/~wdloughman/wdl.htm
|
