Setting Props of Multiple objects with behavior?

[Scott Rossi]

"Automatically" meaning that assigning your behavior to the control is all
that is needed to theme it.

You still need to loop through the controls on the card/in the stack and
apply your custom property (setProp).

Regards,

Scott Rossi
Creative Director
Tactile Media, UX/UI Design




On 9/25/15, 12:42 AM, "use-livecode on behalf of Sannyasin
Brahmanathaswami" <use-livecode-bounces at lists.runrev.com on behalf of
brahma at hindu.org> wrote:

>YepŠ I think I did tooŠ ask beforeŠ
>
>we migrated from Google Mail to Micrsoft365/Outlook and I ³lost² my list
>archives (still in PostBox foldersŠ I have yet to migrate) which I
>usually search in.
>
>"The nice
>thing about using a behavior is that once you establish the theme in the
>behavior script, any control that gets the behavior assigned to it will be
>able to display the theme automatically.²
>
>³Automatically² ? 
>
>But would you not have to trigger the setProp handler some how?
>
>Brahmanathaswami
>
>
>
>
>
>
>
>
>On 9/24/15, 9:35 PM, "use-livecode on behalf of Scott Rossi"
><use-livecode-bounces at lists.runrev.com on behalf of
>scott at tactilemedia.com> wrote:
>
>>I believe you've asked this question before :-)
>>
>>If you can get them to work, the Inspector has a Property Profiles pane
>>that is supposed allow you define named property settings for all
>>controls
>>in your stack, the card, and the stack itself.  I believe the theory is
>>that any built-in LC property can be changed simply by changing the
>>property profile of the stack (and thus all controls in the stack that
>>share that property name will automatically update as well).  The reason
>>I
>>say "in theory" is because the process of applying profiles appears
>>buggy,
>>but that might just be my own cluelessness in getting the settings to
>>stick.  It's a cool idea, it just doesn't seem to work using the
>>Inspector.
>>
>>Another option is to include a setProp handler in the behavior assigned
>>to
>>your controls.  The handler would set the controls' "theme" -- their
>>appearance, location, etc.  You then loop through all controls and set
>>their theme property to whatever value/s you've established.  The nice
>>thing about using a behavior is that once you establish the theme in the
>>behavior script, any control that gets the behavior assigned to it will
>>be
>>able to display the theme automatically.
>_______________________________________________
>use-livecode mailing list
>use-livecode at lists.runrev.com
>Please visit this url to subscribe, unsubscribe and manage your
>subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-livecode