Problem summary
knob.splitivew() in Nuke 10 can split a knob too far, to create a value for a view that doesn't exist. This affects Ocula's VerticalAligner node as the inbuilt button to create a CornerPin node now creates a CornerPin with values for 3 views rather than 2.
Customer reported version
nuke.10.0v4
Customer reported platform
ubuntu
Steps to reproduce
1) Launch Nuke, open the Project Settings (hit S over the nodegraph) and then click on "Set up views for stereo"
2) Create a node and split one of the knobs to have values for both views by running the following
mult = nuke.nodes.Multiply()
mult['value'].splitView(0)
mult['value'].splitView(1)
Note there will now be values for l, r and * views. In Nuke 9 running the same commands just creates values for l and r.
Workaround
Running the knob.splitView() command without specifying a view number will correctly split the knob for stereo scripts. This doesn't work if working without more than 2 views in the script as you need to specify the view to split to.
Reproduced by support
Support has reproduced this with Nuke 10.0v1 and v4 on Windows, Linux and OSX. This doesn't happen in Nuke 9.0v9 or earlier with the same commands.
Expected behaviour
Nuke should only split the knob so there's one value per view.
Actual behaviour
Nuke splits the knob so there's a value for a view that doesn't exist.