show only browse

[Kenneth Brody]

On 9/16/2010 12:31 PM, Richard Kreiss wrote:
[...]
>>>> Well, a "show=only" browse won't wait for anything from the user.  Do
>>>> you have any code after the browse lookup (such as a CLEARB or your
>>>> SWITCHTO) that would take down the browse window?
>>>
>>> No.  Pressing<enter>   or switching screens by pressing their number would
>> bring down the browse window.
>>>
>>> The only function after the browse goes up is an<END>.
>>>
>>> 114  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
>>>          ◄ If:
>>>          Then: lookup tran = transaction  K=16   i=E -Nxm b=(ba&bb&bc)
>>> 115  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
>>>          ◄ If:
>>>          Then: SHOW "";END
>>>
>>> If I insert a line between 114&   115, anything there is ignored.
>>
>> Define "anything".  Define "ignored".

You didn't answer this.

>> What about this line:
>>
>>       mesgbox "I bet this isn't ignored."
>>

Nor this.

>>> I found that one could not capture @sk
>>
>> @SK from what?  @SK is still valid from whatever was the last keystroke read
>> by filePro, but remember that the "show=only" browse lookup doesn't wait
>> for any keystrokes.
>>
>> Okay, so your processing ends.  But, depending on where this processing is
>> being run, some other processing (such as automatic or @entsel) will
>> probably be run.  What happens there?  Do you have anything like CLEARB or
>> SWITCHTO?
>>
>>> AS I mentioned, what I wanted to do is allow the user to return to the
>> original screen if they pressed<enter>.
>>
>> Pressed Enter _when_?
>
> Finished looking at browse the natural instinct is to press<enter>.  This will drop the browse and remain in screen 9.
>
> This routine starts with @key9.  A lookup is done to insure that there are transactions to bring up.  If none, a msgbox appears advising there are no transactions.

But, you END your processing immediately after the browse lookup is done. 
Where, precisely, do you wait for the user to press Enter?

> The browse comes up and shows the transactions and their status.
>
> As for processing, I found that I could drop the browse and return to the original screen but are moved to the next record.  As I think about it, I could use pushkey "[CRUP]"
>
> Just tested this, by placing the pushkey at the end of the auto table, I got the program to move back to the original record.
>
> Thanks for the reply, it made me think this through.
>
> Not sure if there is a more elegant solution but this works.

Why is PUSHKEY needed?

Step back.  Describe what you want to happen.  When is the browse lookup 
supposed to appear?  What's supposed to happen when the browse window is 
shown?  What if the user presses something other than Enter?  (Or do you 
want to wait, specifically, for Enter?)  When is the browse window to be 
taken down?  What should happen after it's taken down?

Etc., etc., etc.

While it may be clear to you, you haven't described it clearly to us.  (Or, 
at least, to me.)  Why are you trying all of these convoluted methods to 
work around some problem that probably doesn't exist, rather than clearly 
define the problem first?

-- 
Kenneth Brody