ID 381401 - Previously disabled knobs appear enabled when promoted from within a Group/Gizmo node.

Problem summary:
Previously disabled knobs appear enabled when promoted from within a Group/Gizmo node.


Customer reported version:
Nuke11.3v1


Customer reported platform:
Windows 7


Steps to reproduce:
1) From Nuke, create a Write node.

2) Ensure that "first" is disabled by default on the Write node.

3) Group the Write node (CTRL+G while the Write node is selected). 

4) Promote knobs from the Write node to Group/Gizmo(right-click in the Properties bin, select Manage User Knobs>Pick), such as "first" or "colorspace".

5) Open the Script Editor and run the following command: print(gizmoName.knob("first").enabled())to verify that it is disabled.

6) Change the value of 'first' to then disable the knob.

7) Enable 'first' using gizmoName.knob("first").setEnabled(True), this will visibly enable it on the UI again. 


Expected behavior:
Disabled knobs that are promoted from within the Group should be visibly disabled in the interface.


Actual behavior:
The knobs on the Group/Gizmo remain visibly enabled until the user changes the knob value. After it becomes disabled, the knob cannot be re-enabled until using Python to set values.


Workaround:
A slight workaround is to enable/disable the knob editing [CTRL+ALT+E] in the Properties bin. This will refresh the knobs for their true values.


Reproduced by Support in: 
Nuke 11.3v5 - Windows 10, CentOS 7, macOS 10.13

Nuke 11.3v1 - Windows 10

Nuke 11.2v1 - Windows 10

Nuke 11.1v1 - Windows 10

Nuke 11.0v1 - Windows 10

Nuke 10.5v1 - Windows 10

Nuke 10.0v1 - Windows 10

Nuke 9.0v1 - Windows 10

Nuke 8.0v1 - Windows 10, CentOS 7, macOS 10.13
 

Earliest version tested:
Nuke 8.0v1 - This issue appears to be in all versions of the product