v11 - Set whether the block is manually enabled or disabled. The user can toggle whether a block is disabled from a context menu option. A block may still be disabled for other reasons even if the user attempts to manually enable it, such as when the block is in an invalid location. This method is deprecated and setDisabledReason should be used instead.
[null,null,["Last updated 2024-09-18 UTC."],[[["`Block.setEnabled()` is obsolete and replaced by `setDisabledReason()` for managing block disabling in Blockly v11 and later."],["It previously allowed manual enabling/disabling of blocks via a user-toggle in the context menu, but other disabling factors could override this."],["This method accepted a boolean parameter, `enabled`, indicating whether the block should be enabled (true) or disabled (false)."]]],["The `Block.setEnabled()` method, now obsolete, controlled a block's manual enabled/disabled state. Users could toggle this via a context menu. The method accepted a boolean parameter (`enabled`) to set the state, with `true` meaning enabled. However, a block could remain disabled due to other factors, such as being in an invalid location. This method has been deprecated in favor of using `setDisabledReason`. It returns nothing (void).\n"]]
