The expression me.parent() on a COMP (/project1/foo/abc) that has a parent connector to another COMP (/project1/foo/xyz) returns the COMP that contains it (/project1), rather than the thing that it’s connected to as a child.
Is that intentional? If so, is there a convenient way to access the parent COMP in the same manner as the TScript expression opparent(".", 0)?
Not a bug. See answer of Markus here: Node parenting inconsistency - #3 by snaut