AE Template buttons

[Azrail]

in order to implement custom UI controls in AETemplate you should use the -callCustom flag of the editorTemplate command.

Here is a snipped from a custom layout just to give you some idea:

global proc AEcnmAttrStrFormatTemplate(string $nodeName)
{
editorTemplate -beginScrollLayout;
editorTemplate -beginLayout "Version" -collapse false;
editorTemplate -callCustom "AEAttrStrFormatVer"
"AEAttrStrFormatVerRepl"
"pluginVersion";
editorTemplate -endLayout;
editorTemplate -endScrollLayout;
}

global proc AEAttrStrFormatVer(string $attr)
{
text -l `getAttr $attr` versionTxt;
}

global proc AEAttrStrFormatVerRepl(string $attr)
{
text -e -l `getAttr $attr` versionTxt;
}

[VesuvianPrime]

What is the third parameter of callCustom?

Also, what does versionTxt do to the label? My MEL is very rusty.

[Azrail]

1. The third parameter is the actual attribute name, for which the current control is created, and which would be passed as parameter to the custom procedures. You can pass as many attributes as needed.

2. 'versionTxt' is just a name for the text widget, so we can later on access it from within the *Repl procedure.

The main idea is that the first one (AEattrStrFormatVer in my example) is (sortof) used to initialize and build the controls for the current node. The second one (AEattrStrFormatVerRepl) is called on every update of the AE, and is responsible for proper updating of the UI, so here you should made any changes, which are supposed to reflect parameters on the node... hope this makes any sense :)

[VesuvianPrime]

Thanks, you've been a massive help. I'd be completely lost without these forums.

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.