ID 331987 - Multiview knobs do not correctly clone link from the new view to the original view, when the original view is calling an expression.

Problem summary
Many nodes in Nuke have the option to split controls into separate views for multiview (stereo/multi-cam) compositing.

Inside of Nuke 11.1v1, if you are using an expression within a value that gets split into two, the newly split view will clone the source expression. If this newly created split view gets parented back to the original view's value (to retain the same value), this will corrupt the original views value.

This only occurs within the Nuke 11.1v1 release on all operating systems and works correctly in Nuke 11.0v4 and earlier releases.

Customer reported version
nuke.11.1v1

Customer reported platform
centos6

Steps to reproduce

Open the attached script, open created Camera and shift between Left and Right view to see the error in the Translate values.

or

1) Open a Nuke 11.1v1 script and set is as a multiview script by opening the 'Views' tab in the Project Settings and selecting 'Set up views for stereo'.

2) create a Camera and open the 'Properties' bin for the Camera

3) Right-click on the animation menu for translate values and select 'edit expressions'  

4) Enter a quick callback expression, for example 'frame' into the x,y and z values.

5) Create a split off left multiview from the translate values.

6) Select the 'Right' view in the Viewer

7) In the animation menu for the Translate values for the Right view, choose 'edit expressions'

8) Add in an expression to link the Right view to the Left view for x,y and z. 

9) Change back to the Left view in the Viewer
Result: You will notice that the original (Left) view controls for the Translate are now 0'ed out. Even though the values are correct in the expression.
​

10) To verify it is the expression, you can remove the expression in the translate animation menu and replace it with numeric values.

11) Save the script, restart Nuke and re-open the script.
Result: The 0'ing our issue is removed

Workaround
Avoid using expressions within values if they are going to be split and re-parented to the original.

Alternatively, link to an external node for linking values. For example, an Axis node can hold the values and the Camera can call the values in.

Reproduced by support
This bug has been reproduced in:
Nuke 11.1v1 - CentOS 6.9 - Windows 7 - MacOSX 10.13

Unable to reproduce bug in:
Nuke 11.0v4 - CentOS 6.9 - Windows 7 - MacOSX 10.13

Earliest version tested
Nuke 11.0v4
- This issue no longer appears in this version and has regressed

Expected behaviour
When linking a split view value to the original (to retain the same value), Using expressions should not break the connection to the original.

Actual behaviour
Linking a split view value back to the original view with an expression will corrupt the original value.