void cxInWdgtDisable(const char *portName)
subroutine cxInWdgtDisable(portName) character *(*) portName
This routine and its companion, cxInWdgtEnable(3E), can be used to make the appearance of module control panels context sensitive.
Advanced module writers occasionally create their own widget hierarchies using cxXtAreaInitialize() and cxXtAreaAttach(). Calling cxInWdgtDisable on the parameter associated with such a hierarchy will have no effect since the IRIS Explorer UI widget is unrelated (in a parent-child sense) to the user-created widget hierarchy.
It is an error to pass the function a portName that is not a parameter port with a widget.
Individual components of widgets can not be disabled (items in an option menu, for instance).
A bug can occur when the user is manipulating a widget while a module is disabling it. This bug has been observed in pushbuttons. The result is that the lighting effect that makes a button look pushed in is reversed. The state of the buttons lighting model remains reversed until the button is pushed again.
Though disabling a widget keeps the user from sending new data values to a module parameter through the disabled widget, nothing keeps the user from sending new values down to a parameter from an upstream widget that is wired into a parameter whose widget has been disabled.