ID 494708 - The onUserCreate() callback always reports the value 1 for 'first' and 'last' frames in a Read node.

Follow
  1. The Foundry SANDBOX
  2. Bug Tracker
  3. Nuke

Problem summary
The onUserCreate() callback always reports the value 1 for 'first' and 'last' frames in a Read node.

Customer reported version
nuke.n/a

Customer reported platform

Steps to reproduce
1) In Nuke, open the Script Editor and run the following code:

#run first
def readOnUserCreate():
    node = nuke.thisNode()
    nuke.tprint('Read frame range:', node['first'].value(), node['last'].value())

nuke.addOnUserCreate(readOnUserCreate, nodeClass='Read')
2) In the Node Graph, Press R and import a file with multiple frames.
3) View Nuke's console for the frame range output.

Expected behavior
The 'last' should be displayed as the correct frame amount.

Actual behavior
The frame values for 'first' and 'last' are always reported as 1.

Workaround
Using onCreate() allows the correct frame value to be displayed.

Reproduced by Support in:
Nuke 13.0v5 - Windows 10, macOS 10.15
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.0v1 - Windows 10
Nuke 9.0v1 - Windows 10, macOS 10.15

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

    We're sorry to hear that

    Please tell us why