ID 347332 - [Not A Bug] Event handlers for a 'node_pasted' event type are never called

Follow

Problem summary:
Users have found that event handlers registered for a 'node_pasted' event type are never called. 
 
The reason for this is that no events of that event type are ever added to Katana's event queue.
 
Unfortunately, Katana does register one event handler for a 'node_pasted' event type, but that appears to be a remnant of Sony's Katana:

>>> 'node_pasted' in Utils.EventModule.GetAllRegisteredEventTypes()True>>> Utils.EventModule.GetNumRegisteredHandlersForEventType('node_pasted')1
Note that, in the current implementation of Katana's event handling mechanism, event handlers can be registered against arbitrary event type names. This means that, in general, the result of Utils.EventModule.GetAllRegisteredEventTypes() should not be taken as the authoritative source for which types of events exist in Katana (as in: which types of events are added to Katana's event queue in response to user interactions).
 
Steps to reproduce:
  1. In the Node Graph tab, create a PrimitiveCreate node, and select it.
  2. Execute the following snippet of code in a Python tab:
    • 
      def on_node_pasted(args):    pprint.pprint(args)Utils.EventModule.RegisterCollapsedHandler(on_node_create, 'node_create')
  3. In the Node Graph tab, copy and paste the PrimitiveCreate node by pressing Ctrl+C and Ctrl+V.
  4. Inspect the terminal and Python tab for messages.
Expected behaviour:
The details of the node that is created as part of pasting the copied node are shown in the terminal or the Python tab.

Actual behaviour:
The event handler is not called, so nothing is printed from it.

Workaround:
None.
 
Customer reported version:
Katana 2.6v4

Customer reported platform:
CentOS 7

Reproduced by support:
  • Katana2.6v4 - CentOS6.9 - Windows 7
  • Katana2.6v1 - CentOS6.9 - Windows 7
  • Katana2.5v7 - CentOS6.9 - Windows 7
  • Katana2.5v1 - CentOS6.9 - Windows 7
  • Katana2.1v6 - CentOS6.9
  • Katana2.1v1 - CentOS6.9
  • Katana2.0v1 - CentOS6.9
Earliest version tested:
This issue appears to affect all versions of the product.

    We're sorry to hear that

    Please tell us why