ID 327012 - Typo in 'colorspaces.py' causes error callback

Follow

Problem summary
There is a 'Typo' within the 'colorspaces.py' plugin file located in "/*NUKE_VERSION*/plugins/nuke/colorspaces.py"

The problem in-particular is due to the misspelling of 'Nuke.thisClass()' as 'Nuke.theClass()'

This will cause the function to error, as it is not a recognisable attribute.

Customer reported version
nuke.11.1v1

Customer reported platform
windows8

Steps to reproduce

1) In Nuke, Open the Script Editor.

2) Copy/Paste the following script and execute it:

def myfunc(colorspaceName, dataTypeHint):    return Nonenuke.addDefaultColorspaceMapper(myfunc, nodeClass="Read")
3) In your Node Graph, Create a 'Read' node.

Result:  Your 'Read' node will execute an error, the following will appear in your Nuke Terminal:

Traceback (most recent call last):File "/*NUKE_VERSION*/plugins/nuke/colorspaces.py", line 159, in defaultColorspaceMapper"expected string or None"%( nuke.theClass() ) )AttributeError: 'module' object has no attribute 'theClass'

Workaround
1) Copy your 'colorspaces.py' file to an editable location (e.g desktop)

File is located in the following for Windows "C:/Program Files/*NUKE_VERSION*/plugins/nuke/colorspaces.py"


2) Open colorspaces.py in a text editor.

3) Find 'theClass' with 'Ctrl+F'.

4) Replace 'theClass' with 'thisClass'.

5) Save and Replace the colorspace.py file in your Nuke directory.

6) Restart Nuke and test your script. 

Reproduced by support
This bug has been reproduced in:
Nuke11.1v1 - Windows 7 - Mac10.13 - CentOS6.9
Nuke11.0v3 - Windows 7 - Mac10.13 - CentOS6.9
Nuke11.0v1 - Windows 7 - Mac10.13 - CentOS6.9
Nuke10.5v6 - Windows 7 - Mac10.13 - CentOS6.9
Nuke10.5v1 - Windows 7 - Mac10.13 - CentOS6.9
Nuke10.0v6 - Windows 7 - Mac10.13 - CentOS6.9
Nuke10.0v1 - Windows 7 - Mac10.13 - CentOS6.9

Earliest version tested
Nuke10.0v1 - This feature did not exist before this version 
Expected behaviour
The function should work without issues.

Actual behaviour
A typo has kept the function from working correctly and calls an error.
 

    We're sorry to hear that

    Please tell us why