Behavior Nightmare

[Scott Rossi]

Recently, Josh Mellicker wrote:

> On Feb 13, 2010, at 1:21 PM, Scott Rossi wrote:
> 
>> The reason for all the jumping through hoops here is password protection: I
>> need to be able to dynamically add and remove groups from the main stack,
>> and this can't happen if the stack is password protected.
> 
> Doesn't setting the passkey of the stack allow you to add, delete, copy
> groups, etc.?

One of the main benefits of behaviors, from the docs:

"The button containing the behavior script can be located anywhere. In
particular this allows for it be located in a password protected stack,
allowing you to protect the script without need to protect the controls
using it."

It would seem using behaviors is more secure than temporarily removing
security from a stack.

Regards,

Scott Rossi
Creative Director
Tactile Media, UX Design