FWD » Core Development » User Interface

Testcases are attached. 4GL allows to set SCREEN-VALUE for a column (even for an non-ediable browse) and then save it to a record (using, say, ASSIGN INPUT). There are two issues:

1. FWD may lose the SCREEN-VALUE state when the current row goes out of the view, if the column/browse is read-only.
2. 4GL has a quirk: If a row hasn't been edited, but a SCREEN-VALUE has been assigned to a cell of this row, then, if the current row goes out of the view and returns, it visually loses updated SCREEN-VALUE, using the value from the database. But, actually, updated SCREEN-VALUE is persisted and can be interrogated by reading SCREEN-VALUE or calling ASSIGN INPUT BROWSE.
   As a consequence of this quick, when you leave a "quirky" row in FWD, it resets the assigned SCREEN-VALUE immediately, which may look visually unpleasant, but technically it depicts what's happening under the 4GL hood in this scenario.