Flynet Simulated Host

SaveScreen Tag

SaveScreen Tag

Previous topic Next topic  

SaveScreen Tag

Previous topic Next topic  

Save active screen buffer

 

The Simulated Host allows multiple screens to be saved by name, for later restoration.  This is particularly useful when implementing a "stack" organized transaction where a PF key can load one screen, and the PF3 might return to the previous screen.

 

Note that at the time of the SaveScreen, the last screen sent is associated with the saved screen information, not the current screen executing.  For example:

 

ScreenA has an OnInput that checks for PF1, in an IfAid
The PF1 IfAid inside ScreenA performs a ScreenSwitch to ScreenB
ScreenB has a defined OnLoad event which performs a SaveScreen
The screen that will be reloaded on a RestoreScreen will be ScreenA because it was the last screen sent prior to the SaveScreen

 

By using SaveScreen and RestoreScreen, the contents of a screen (including input from the client/emulator) can be restored faithfully rather than from the fixed format of the originating MAP.

 

Attributes:

 

Attribute

Default / Required

Description

name

"save"

Name of the screen to save-- if omitted, the default of "save" is used.  There is no limit to the number of names used, but only one screen at a time may be saved under each name.

 

SaveScreen has no children.


Example:

 

<Script event="onload">

  <SaveScreen name="helpsave"/>

  <LoadMap name="default"/>

  <SendScreen clear="yes" unlock="yes"/>

  <ReceiveInput/>

</Script>