Clearer UI For FilterPlug Inside Python Node?

[danieldresser-ie]

Yannic observed today that the UI for a FilterPlug connection inside a Python node can be extremely counter-intuitive.

If you make a Python node containing a scene node with the FilterPlug is directly connected to the parent ( which is a pretty natural thing to do ), then when viewing the Filter tab of the internal node, you see that the connected filter is the parent node, and you get a list of all the parameters of parent.

I debated whether to file this as a bug report or a feature ... but it's really not a bug - it is showing you the parameters of the connected node.

But it would probably give a result that is much closer to what someone might expect if the search for a connected filter ignored plugs with Direction == In ... then the internal node could show the actual PathFilter or whatever is connected to the parent, which is probably more what someone would be expecting to see.

[johnhaddon]

Yeah, I think we want to use plug.source() to find the eventual source of the connection, not just the immediate input. And then we only want to show the node if it is actually a Filter node. Could you add this to your todo list please Daniel?