PRACTICAL GUIDEUnder review
DisableControl / EnableControl
Records two historical control-enabling calls.
Overview
The eAdvpl guide lists DisableControl(oObject) and EnableControl(oObject). DisableControl has an apparent wording error: its purpose says enable while the parameter says disable. This page records the inconsistency and treats the pair as historical, without asserting compatibility with current objects. Disabled visual controls do not enforce write authorization. The example only prepares callbacks for a caller-supplied object. (Guia de referência eAdvpl, n.d., sections 3.28–3.29, p. 21, ref. 1)
Commented example
// Historical reference; callbacks are not invoked.
bDisable := {|oControl| DisableControl(oControl)}
bEnable := {|oControl| EnableControl(oControl)}Expected result
No control changed; availability and accepted type require validation. Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.
- Prefer the documented contract of the actual component.
- Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.
Comments
There are no approved comments yet.
Sign in with Google or Microsoft to comment.