[ |../../index.htm#lansa/dsnba_0050.htm]
You are here:

10.7 Invoking an Action Bar as a Process

When you elect to use a process that is of type "ACT/BAR", its action bar control table entries are examined and used to assemble an action bar.
It will clear the screen, and then appear like this (1 to 6 action bar options):
  Action 1   Action 2   Action 3   Action 4   Action 5  Action 6  
 _______________________________________________________________
  
 
Or, like this (7 to 12 options):
 
 Action 1  Action 2  Action 3  Action 4   Action 5  Action 6  
 Action 7  Action 8  Action 9  Action 10  Action 11 Action 12 
 _____________________________________________________________
  
 
Or even like this (13 to 18 options):
 
 Action 1  Action 2  Action 3  Action 4  Action 5  Action 6  
 Action 7  Action 8  Action 9  Action 10 Action 11 Action 12 
 Action 13 Action 14 Action 15 Action 16 Action 17 Action 18 
 _____________________________________________________________
  
 
Some things that should be noted about the invocation of an action bar process are:

• The lower portion of the screen (below the action bar) is erased. When an action bar process is invoked it erases the screen, rather than overlaying what is currently on the screen. This gives the user the visual feedback that they have "started something new" (ie: are working with a new action bar).
• Choices may be unavailable. The availability/unavailability is established from the action bar control table (initially) and then controlled by invoked RDML functions by using the SET_ACTION_BAR built in function.
• The Exit function key will be enabled (unless specifically disabled at the process level as part of the partition definition). If used it will act just as it would if the process was presented as a menu.
• The Cancel function key will be enabled (unless specifically disabled at the process level as part of the partition definition). If used it will act just as it would if the process was presented as a menu.

[ |../../index.htm#lansa/dsnba_0050.htm]