🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: bit.listserv.xedit-l
Article #810

Re: Refresh Subcommand

#810
From: Bill Harvey
Date: Sat, 09 May 1992 02:21
52 lines
2812 bytes
On Thu, 7 May 1992 11:30:28 EDT, Tom True <TDTRUE@PUCC.BITNET> said:
>I've run into a slight problem with an application that uses XEDIT as
>a screen manager.  Lately, some programs that are called by the application
>have taken more than a few seconds to complete.  To reassure the user
>I want to display messages that document the progress of the command.
>Unfortunately, the only way I can get a changed 'RESERVED' line on the
>screen is by issuing 'REFRESH'.  This works, but unlocks something:

I'm no expert, but as near as I can tell, REFRESH does not inherently unlock
the keyboard.  Are you sure it's not unlocked already?  And you just don't
notice it, unless REFRESH is in use?

>                                                                    if the
>user hits 'ENTER', the screen clears and a VM READ is given.

This might be the key.  Do you get the VM READ after ENTER even if you
don't use REFRESH?  If so, then the keyboard is unlocked, and it only
becomes annoying because REFRESH won't clear the screen.

>                                                             Another press of
>'ENTER', and the application is RUNNING again. If I try to redisplay the
>screen again with another 'REFRESH', the user gets a 'MORE ...'.  As long
>as I avoid 'REFRESH' and just use the 'READ' subcommand I avoid the problem,
>but cannot update the screen at will.

This might be the real problem.  If I remember right, READ does an automatic
screen clear;  REFRESH won't.  If that's the case, you might try to force
the screen clear just before the REFRESH.  Something like:

MyRefresh:  Procedure
   If Externals() > 0 Then   /* the user hit ENTER!  Shame, shame, shame! */
        'VMFCLEAR'
   'REFRESH'
   /* let's empty the Externals() buffer.  Should be careful here!  Depending
    * on the circumstances, this could be a Bad Thing!    */
   Do While Externals() > 0
      Pull .
   End
Return


>Any suggestions on how to avoid this problem?

Well, that's all *I* can think of.

>                                              Or on where else to ask?

Nope.  This is the place.  If you can't find the answer here, the answer
probably doesn't exist!  :-)

Bill
>Tom True
Technical Details
Message-ID: <92129.115721HARVEY@wuvmd.wustl.edu>
Path: arc1-ca.pugleaf.net!sparky!uunet!wupost!wuvmd!harvey
References: <XEDIT-L%92050711314374@RUTVM1.BITNET>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10c92b,74333c7168f8d5c6
X-Google-Attributes: gid10c92b,public
X-Google-ArrivalTime: 1992-05-08 19:21:58 PST
Path: arc1-ca.pugleaf.net!sparky!uunet!wupost!wuvmd!harvey
Organization: Washington University, St. Louis
Message-ID: <92129.115721HARVEY@wuvmd.wustl.edu>
Date:         Fri, 08 May 92 20:21:58 CST
From:         Bill Harvey <HARVEY@WUVMD.Wustl.Edu>
To:           NETNEWS@WUVMD
Subject:      Re: Refresh Subcommand
Newsgroups:   bit.listserv.xedit-l
References:    <XEDIT-L%92050711314374@RUTVM1.BITNET>
Lines: 52