Project

General

Profile

Feature #4341

CREATE-RESULT-LIST-ENTRY missing implementation features

Added by Stanislav Lomany about 7 years ago. Updated 14 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
10/05/2019
Due date:
% Done:

0%

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

browse-insert-from-fillin.p Magnifier (737 Bytes) Stanislav Lomany, 10/05/2019 05:14 PM

Related issues

Related to User Interface - Feature #3940: CREATE-RESULT-LIST-ENTRY() method support Closed

History

#1 Updated by Stanislav Lomany about 7 years ago

The following CRLE-related features are not implemented:
  1. Implementation for CRLE/DRLE for non-scrolling queries - needs much effort to implement and is not practically used.
  2. CRLE for the last entry in the result list - 4GL behavior seems to be unpredictable. Details are in #3940-22. Browse works fine because of the 4GL trick described in #3940-23.
  3. Browse mode when INSERT-ROW creates an in-row fill-in which is active even when the browse is not focused. Done by a trigger with INSERT-ROW if the current widget is not a button. See the attached testcase as an example. The behavior should be checked for a variety of widget and event types.

#2 Updated by Stanislav Lomany about 7 years ago

  • Related to Feature #3940: CREATE-RESULT-LIST-ENTRY() method support added

#3 Updated by Greg Shah 14 days ago

We have a project that needs item 3 of this task, the INSERT-ROW focus case. The other items, for CREATE-RESULT-LIST-ENTRY on non-scrolling queries and on the last result-list entry, are not needed for it.

Its cash entry screen calls INSERT-ROW from triggers whose current widget is not a button, and immediately moves focus into the new row:

ON TAB OF fi_customer IN FRAME f_head DO:
   br_main:INSERT-ROW("BEFORE") IN FRAME f_main.
   APPLY "ENTRY" TO tt_line.part-id IN BROWSE br_main.
END.

The same sequence runs from RETURN on a fill-in in another frame, from ANY-KEY of a browse cell, from ROW-LEAVE of the browse, from BACK-TAB of a cell in a second browse, and from CHOOSE of a button.

Please write testcases with an OpenEdge baseline for each of those triggers. Record where focus ends up and what can be typed into the new row, and fix what differs. The event order around INSERT-ROW in #5971 (ENTRY, LEAVE, ROW-ENTRY, ROW-LEAVE, VALUE-CHANGED) should be checked in the same testcases, because the screen has ROW-LEAVE logic.

Also available in: Atom PDF