jeffledbetter
Member
Hi.
Perhaps I am overlooking the obvious.
Thinking about migrating our procedural based that dynamically creates a browse widget.
If I create a browse widget in a class file, is there an equivalent to the PERSISTENT RUN statement that is used in a trigger? Or, does the entire trigger code need to be defined in the ON of the TRIGGERS block? Or something else?
Perhaps I am overlooking the obvious.
Thinking about migrating our procedural based that dynamically creates a browse widget.
If I create a browse widget in a class file, is there an equivalent to the PERSISTENT RUN statement that is used in a trigger? Or, does the entire trigger code need to be defined in the ON of the TRIGGERS block? Or something else?
Code:
CREATE BROWSE hBrowse
ASSIGN
ALLOW-COLUMN-SEARCHING = TRUE
FRAME = phHostFrame
ROW-MARKERS = plMarkers
SENSITIVE = TRUE
SEPARATORS = plSeparators
MULTIPLE = plMultiple
VISIBLE = TRUE
TRIGGERS:
ON ROW-LEAVE PERSISTENT RUN row_leave IN THIS-PROCEDURE.
ON START-SEARCH RUN sort_browse IN THIS-PROCEDURE.
ON VALUE-CHANGED PERSISTENT RUN value_changed IN THIS-PROCEDURE.
ON MOUSE-SELECT-DBLCLICK PERSISTENT RUN dbl_click IN THIS-PROCEDURE.
END TRIGGERS.