COMMANDUnder review

@ ... METER

@ nRow, nCol METER oMtr [FROM nFrom TO nTo] [SIZE nWidth, nHeight] OF oWnd

Visually represents processing progress.

@ ... METERAdvPL

01 · OVERVIEW

Overview

The eAdvpl reference guide, §3.23–3.24, p. 20, records the historical variant shown in the syntax. Fragments assume the matching environment and command definitions; they are not a complete application. The historical variant provides FROM/TO bounds and SetMeter updates. TMeter documents a total and Set/SetTotal methods: these distinct contracts must not be merged into invented syntax. Visual progress should reflect completed work rather than attempts. The fragment uses ten non-writing steps and does not implement cancellation or real-task error handling. (Refs. 1–2)

02 · SYNTAX

Syntax

@ nRow, nCol METER oMtr [FROM nFrom TO nTo] [SIZE nWidth, nHeight] OF oWnd

Parameters

nRow, nCol

NumericRequired

Origin position in the units of the selected variant.

oWnd / oDlg

ObjectRequired

Existing parent window; use the identifier from the actual code.

Return value

Interface/printing command; do not use as a function-return expression.

03 · PRACTICAL EXAMPLE

Commented example

// Historical fragment; oDlg already exists.
Local oMtr
Local nStep
@ 2, 2 METER oMtr FROM 0 TO 10 SIZE 30, 1 OF oDlg
For nStep := 1 To 10
    // Teaching step; replace with genuinely completed work.
    SetMeter(oMtr, nStep)
Next

Expected result

Proposes progress from 0 to 10. A fast loop may show only the final state; it does not establish responsiveness. Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.

BEST PRACTICES

Handle zero totals and partial failure. Do not add Sleep merely to simulate work; separate visual updates from transaction confirmation.
Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.