FW: Code & screen shot - HTML formatted email

[Kenneth Brody]

On 3/19/2010 10:57 AM, Richard Kreiss wrote:
[...]
> Tested Bill's suggestion that I stop auto processing from running as the
> show window comes up first, then auto processing runs causing the bleed
> through.
>
> This worked with one caveat,

That tells me that you were doing what I said back on Tuesday:

> Have you modified the values of the fields that bleed through?  Try putting
> a DISPLAY before your MEMO command, to make sure the screen have been
> refreshed first.  Or, perchance, do you modify the fields "under" the popup
> after it is shown, but before it's taken down?

Your automatic processing is probably modifying fields "under" the popup.

> the white line boarder around the window disappears in sections.

My guess is that those are simply blank fields that happen to be under the 
border that are bleeding through.

> One other question which arose during this test, I used putenv "isshow","y"
> in input and then checked it in auto to end the auto processing.
>
> When I used putenv "isshow","N" at @keyC which cleared the memo window, the
> value did not change.  Is this value locked for the remainder of this clerk
> run or should it have been changed when a new putenv was issued?

GETENV() returns the current value, and PUTENV will change that value.

::end:
@entsel::show "isshow='" & getenv("isshow") & "' -- \{C} to change it":
::end:
@keyC::xx(20,*) = getenv("isshow"):
::input popup xx "New isshow> " default:
:@sk ne "brky":putenv "isshow", xx{"":
::end:

-- 
Kenneth Brody