Unexpected Parent Shortcut Behaviour (TD.32820 Win11)

General TouchDesigner Discussion
1

Hi! I’m struggling a bit in the usage of the Parent Shortcut. In the example file below I have a parent shortcut ‘TEST’ on the project1 base. I want this shortcut to access the custom pars of project1 base from anywhere in the project.

When you go into the project1 in my example file you see two bases: ‘toBeCopied’ and ‘toBeCopied1’. In this instance I created toBeCopied. In this base you can find 2 bases: ‘A’ and ‘B’. A has a custom par float1, and B has a Parameter CHOP inside. When referencing A to this Parameter CHOP, TD automatically fills in: parent.TEST.op(‘toBeCopied/A’). Now the name toBeCopied is hardcoded. When I copy the base (creating ‘toBeCopied1’), the parameter CHOP still looks at parent.TEST.op(‘toBeCopied/A’). Shouldn’t it just fill out parent(2).op(‘A’)?

Ideally I would like to use the parent shortcut to only acces the custom pars of that OP, and keep the rest of the references relative.

weirdParentShortcutBehaviour.3.toe (3.7 KB)

2

Ah I think I found the solution: Each comp that can be copied/needs to be modular has to have a Parent Shortcut. So in my previous example I’d need to give ‘toBeCopied’ a Parent Shortcut.