Project

General

Profile

Bug #5153

improvements to down body processing

Added by Greg Shah about 3 years ago. Updated about 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:

History

#1 Updated by Greg Shah about 3 years ago

1. Should we just add this processDownBody() to handleScreenBuffers()? If the downConfigs are non-null then we process it. For LT.clearAll(), LT.view() and LT.choose() this also has the advantage of not being hard coded to the sb[0] which is a poor design in my opinion.

2. Should we be sending/processing the down body state for more statements than we do today (CLEAR ALL, VIEW, DOWN, pushScreenDefinition() and CHOOSE)? For example, UP seems to be an obvious one that might change the down body state. I also wonder about WAIT-FOR but I'm not sure that a user generated event and change the current iteration.

Also available in: Atom PDF