FWD » Core Development » User Interface

There're cases which I consider as quirks which are related to VALUE-CHANGED event. Under specific circumstances, this event is NOT fired while the actual set of selected rows has changed.

Testcase:

def temp-table tt field f1 as integer
field f2 as char
field f3 as char format "x(20)".

def var rid as rowid.
def var i as integer.
repeat i = 1 to 50:
  create tt.
  tt.f1 = i.
  tt.f2 = "Test " + string(i).
  tt.f3 = "Character " + string(i).
end.

def query q for tt.
def browse brws query q DISPLAY tt.f1 width 25 tt.f2 tt.f3
   WITH 10 DOWN multiple.
OPEN QUERY q FOR EACH tt.

def button btn1.
form brws with frame fr1.
enable all with frame fr1.

def var cnt as integer.
on "value-changed" of browse brws do:
    cnt = cnt + 1.
    message "changed" cnt.
end.

message "Case 1: Click row 2, ctrl+click row 5, click row 5. In 4GL VALUE-CHANGED event is not fired.".
message "Case 2: Click row 2, ctrl+click row 5, shift-click row 5. In 4GL VALUE-CHANGED event is not fired.".

wait-for close of current-window.

VALUE-CHANGED behavior is full described in #9862-39