PRACTICAL GUIDEUnder review

FWMarkBrowse and multiple browses

Plans marking and multiple-browse context.

FWMarkBrowse and multiple browsesAdvPL

01 · OVERVIEW

Overview

FWMarkBrowse uses FWMBrowse internally and adds marking/buttons. Documentation excludes native array-backed data support. Each browse needs a coherent owner, alias and configuration; profile identity distinguishes preferences in multi-browse routines. Marking is neither a business lock nor batch validation. The fragment constructs two components without data, activation or marking. Applications must clean up each component and preserve alias context while processing selections. (Sources: refs. 1–1.)

03 · PRACTICAL EXAMPLE

Commented example

#Include "Protheus.ch"

User Function Ed437()
    Local oFirst := FWMarkBrowse():New()
    Local oSecond := FWMarkBrowse():New()
    // No Activate or AllMark: data has not been configured.
    FreeObj(oFirst)
    FreeObj(oSecond)
Return Nil

Expected result

Two independent objects created and freed without a UI. Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.

BEST PRACTICES

Validate selection and concurrency during processing beyond mark appearance.
Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.

FWMarkBrowse and multiple browses

Overview

Commented example

Related content

Comments