ID 81387 - Port connection issues when using multiple nested groups within each other

Follow

Problem summary
When using nested groups, users will find that any nodes within the nested group, cannot be connected to the outer-most group.
 
 
The issue is related to the position of the Group bubble of the nested Group node: The return port and output port, and a connection going into the return port of a nested Group node cannot be accessed if the Group bubble appears outside of the bounds of the parent Group bubble.
 
Video example:
 
Customer reported version
    katana.2.6v4 
 
Customer reported platform
  centos7 
 
Steps to reproduce
1. Create a Group node, rename it "GroupA"
2. Create a Dot node.
3. Within GroupA create a Group node, rename it "GroupB"
4. Within GroupB create a CameraCreate node
5. Connect the CameraCreate node to the Dot node
6.  At the root level of the node graph, expand group 'bubbles' for GroupA and GroupB.
7. Try to select or edit the connection between the CameraCreate node and the GroupB's return port.
Result: The connection results are  locked while it shouldn't be.
 
Workaround
 
Option 1
Move the child Group bubble into the bounds of the parent Group bubble.
This will allow you to select the ports correctly
 
Option 2
 Enter the parent Group node, so that the nested Group bubble is contained within the parent Group bubble bounds.
 
Option 3
Use the port keyboard shortcuts ('1' through to '9') to connect nodes works as expected.
 
If using the keyboard shortcut method with nodes with more than 9 inputs, you could select your output, then use the keyboard shortcut for the input.  From here, you can select the connection, and edit which input port it is connected to.
 
Option 4
You can use the Python tab to connect the ports.
 
Please check out the link below for more information on connecting nodes with Python:
 
Reproduced by support
 
This bug has been reproduced in:
Katana2.6v4 - Windows 7 - CentOS6.9
Katana2.6v1 - Windows 7 - CentOS6.9
Katana2.5v7 - Windows 7 - CentOS6.9
Katana2.5v1 - Windows 7 - CentOS6.9
Katana2.1v6 - CentOS6.9
Katana2.1v1 - CentOS6.9
Katana2.0v1 - CentOS6.9
 
Earliest version tested 
- This issue appears to be in all versions of the product
 
Expected behaviour
Nested group node outputs should be able to connect to parent nodes.
 
Actual behaviour
Nested group node outputs are not select-able with the mouse
 

    We're sorry to hear that

    Please tell us why