Project

General

Profile

Bug #5300

4GL quirk about assigning SCREEN-VALUE in an editable browse

Added by Stanislav Lomany about 5 years ago. Updated about 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
04/30/2021
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

screen-value-test.p Magnifier (929 Bytes) Stanislav Lomany, 04/30/2021 02:37 PM

screen-value-test-ed.p Magnifier (987 Bytes) Stanislav Lomany, 04/30/2021 02:37 PM

Related issues

Related to User Interface - Bug #2596: Implement missing browse quirks. New 06/26/2015

History

#1 Updated by Stanislav Lomany about 5 years ago

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.

#3 Updated by Greg Shah over 4 years ago

  • Related to Bug #2596: Implement missing browse quirks. added

Also available in: Atom PDF