| GENERAL DESCRIPTION |
Request: Use of the routine calls REFRESH^VALM and
RESET^VALM4:VALMCC
Input: none
Output: none Purpose: These calls are used to refresh the screen and reset
the
scrolling area while program control remains within an
action (as opposed to performing the same action when exiting
an action, which is accomplished by setting VALMBCK="R").
Request permission to set the variable VALM("PROTOCOL"). The purpose of
setting this variable is to be able to define the specific protocol to be
executed for a list template, as opposed to defining three identical list
templates, all with different protocol menus.
Resetting VALM("PROTOCOL") resets the protocol menu. This allows having the
same list manager definitions for a screen that may have different input
capabilities, for example one with input and one just view only actions.
RESET^VALM4 can ONLY be called if VALMCC is high(1)
The context for these calls are as follows: The calls will be made within a
List Manager application, specifically within various options of the Encounter
Form Utilities. The reason for making the calls is that we want to be able to
display an encounter form in the top part of the screen while having a
dialogue with the user in the bottom part of the screen. The problem is that
it is necessary to call FileMan at certain points within the dialogue. FileMan
assumes it has the entire screen at its disposal, so when it communicates with
the user the display#is likely to scroll out of the scrolling area on the
bottom of the screen, so the user is unable to read what FileMan displays. To
avoid that, what we do is: 1) Everywhere FileMan is called in the situation
described above we call FULL^VALM1. That sets the scrolling area to the entire
screen. 2) When the problem point is passed and we want to continue the
dialogue with the encounter form displayed at the top we call REFRESH^VALM to
redraw the screen. Then we call RESET^VALM4 to reset the scrolling area so
that the dialogue can occur on the bottom of the screen with the form
displayed at the top.
VALMCC is an input variable to RESET^VALM4. VALMCC must test true or
RESET^VALM4 should not be called. There are dozens of variables that are set
by the List Manager, but those are part of the internal workings of the List
Manager and are not the concern of this application. There are some List
Manager variables that the application is responsible for setting, but those
are well documented by the List Manager, i.e., they are not specific to
calling these entry points.
The context is that the List Manager has been called. Then, from within the
List Manager, the user has selected an action, which invokes a protocol. The
protocol invokes a routine, which is where those calls are made.
|
