#startAA and #endAA fix in macros

[slolic]

[spin-off from http://forum.percussion.com/showthread.php?t=467]

Couple of questions regarding #startAA and #endAA bracketing:

1. is this required for all macros even though AA is not used in Edit mode
2. does it apply only to macros in \rx_resources\vm\rx_assembly.vm or macros in all templates

Thanks…

[rljohnson]

Sinisa,

@slolic;1995

1. is this required for all macros even though AA is not used in Edit mode[/QUOTE]

Use of the #startAA<object> and #endAA<object> is only required for macros and Templates where you want the fields to be editable using the Active Assembly interface. If you do not use these macros to encapsulate an object, the fields within it will not be editable in that interface.

[QUOTE=slolic;1995]2) does it apply only to macros in \rx_resources\vm\rx_assembly.vm or macros in all templates

The system macros (defined in \sys_resources\vm\sys_assembly.vm) already include the #startAA<object> and #endAA<Object> macros. You only need to include them in your custom macros (stored in the file you cite) or in manual Velocity in your Template if you want to allow editing of the fields using the Active Assembly interface.

RLJII

[slolic]

That explains it.
Thank you.

[Andrew_Morrison]

Hello,

When I try adding calls to #startAAField and #endAAField to a macro I’ve written to display multiple-valued fields, it doesn’t work. At the bottom of the Active Assembly interface the following message is displayed:

FATAL exception raised: 'this.objId.getFieldLabel()' is null or not an object

Is this a bug I should raise with support, or does Active Assembly just not work with multiple value controls like sys_DropDownMultiple?

Thanks,

Andrew.