Problem summary
Nuke's Python Api call getValueAt does not call the correct view within multi-viewer knobs
Customer reported version
nuke.10.5v5
Customer reported platform
centos6
Steps to reproduce
1) Within your project settings ("S" on nodegraph) create two views, and name them "left" and "right" respectively.
2) Create a Blur node and split the views; Select the icon that looks like an image pane and a slightly darker image pane, and select "split off left"
3) Assign the left and right values to be arbitrary numbers, eg 5 and 10. (5 left, 10 right)
4) With the blur node selected and your view set to "right" run the following script within the script editor.
size = nuke.selectedNode()['size']print size.getValueAt(1, view='right')
5) The printed result will state "Result: 10.0" indicating that the blur value on the right viewer is set to 10.0 as placed in the Blur node.
6) However, if you set the viewer to left but keep the script the same and execute it, it will return 5 despite the script calling for the "right" view.
Workaround
For Nuke versions released after Nuke 10.0v1, set the active view then run the call to get the values for that view, then switch the active view and run the call again to get the values for the other view.
Reproduced by support
Nuke 11.0v2 - CentOS 6.9 - MacOS 10.13 - Windows 7
Nuke 10.5v6 - CentOS 6.9 - MacOS 10.13 - Windows 7
Nuke 10.5v1 - CentOS 6.9 - MacOS 10.13 - Windows 7
Nuke 10.0v6 - CentOS 6.9 - MacOs 10.13 - Windows 7
Nuke 10.0v1 - CentOS 6.9 - MacOS 10.13 - Windows 7 - first repro'ed
Nuke 9.0v9
Nuke 9.0v1
Nuke 8.0v6
Nuke 8.0v1
Nuke 7.0v10
Earliest version tested
Nuke 7.0v10
Expected behaviour
Nuke would state the correct viewer that is being called eg.
print size.getValueAt(1, view='right')
would print the blur values of the right viewer
Actual behaviour
Nuke prints the output of the currently selected viewer within the viewport, instead of the one specified by the command.