Another one: Why don't brwlook show-only's in auto run every time?

[Jay R. Ashworth]

On Mon, Dec 03, 2007 at 10:33:49AM -0500, Kenneth Brody wrote:
> Quoting Jay R. Ashworth (Sun, 2 Dec 2007 18:33:53 -0500):
> >I have this brwlook in my automatic processing:
> >
> >::lookup slips = ttmslipe  k=1    i=c -nxm b="(brw=14,7,1 show=only
> >fill=desc,top)[Slip     Type    Tech    Desc:
> >::                    Comment]*1       *2      *7      *3
> >*131":
> >
> >When I select a record from the index or browse, I get the brwlook.
> >
> >But if I then use the arrow keys to move up and down the index, I don't
> >get the browse, even when there are records that should match it.
> 
> What do you mean by "move up and down the index"?  Are you scrolling
> through the browse, or some other screen?  If you're on the full screen
> showing the record, then moving up and down through records will run
> the automatic processing, and will show the brwlook if you execute it.

I mean that if I go to Index Selection, and pick the first record of
the index, I will go to the selected screen and the browse will display
correct (as I want it to).  If I then use KDWN to go to the next
record, the browse will disappear, and never redisplay, no matter which
record I navigate to with the arrows.

> >If I go directly to those records, I do get it, with the proper
> >contents.  Shouldn't it happen every time automatic runs?  Automatic
> >runs every time I position myself onto a new record, right?
> 
> "It works here".

Um, *what* works there?  :-)

> >Or is this one of those nasty interactions with "automatic runs three
> >times, and there isn't a system variable to tell you which of the three
> >runs it is?"  :-}
> 
> Well, the "it runs three times" isn't entirely true.  I assume you are
> referring to:
> 
>     1:  You first read and display the record, which runs automatic.
>     2:  At some later point in time, you enter update mode, at which
>         point the record is read again, and automatic processing is
>         run "a second time".
>     3:  After you save the record (and you're not in "add records" mode,
>         or something else which will cause you to go to another record),
>         filePro re-reads the record (in non-update mode) and runs
>         automatic processing "a third time".
> 
> Yes, the above scenario causes automatic processing to run three times,
> but that's because three distinct events have occurred to trigger it,
> with each one running it once.

Sure.  But it doesn't seem to be behaving as I desire: when I navigate
to the second record, the lookup command is *clearing* the leftover
browse, and not displaying a new one.

Cheers,
-- jra
-- 
Jay R. Ashworth                   Baylink                      jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com                     '87 e24
St Petersburg FL USA      http://photo.imageinc.us             +1 727 647 1274

	     Witty slogan redacted until AMPTP stop screwing WGA