If you don't mind nesting your navbar within a separate group, another option is to have an empty group already assigned to all your cards -- when the navbar group is copied over to your stack, it will automatically be available on all appropriate cards.
Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 4/17/16, 1:25 PM, "use-livecode on behalf of Sannyasin Brahmanathaswami" <[email protected] on behalf of [email protected]> wrote: >[email protected]> wrote: > > > >>I have a couple that delete if exists from the second stack, copies from >>first to send, and then places on every card. >> >>You could also have a custom property for cards indicating whether or not >>it should be placed on them. > >This makes sense so how do you do it. > >I¹m thinking this (pseudo code, yet to be tested) > >On preopenStack > # assume the main stack the trigger this is still open > # but on Mobile the new stack will take over the screen > # where > Copy group ³bottomNavBar² of stack ³mainStackName" to card 1 of this >stack >Set the bottom of group ³BottomNavBar² of card 1 of this stack to the >height of this stack >Repeat with x - 2 to the number of cards of this stack > If the uHasBottomNav of card x of this stack = ³true² then > Place group ³bottomNavBar² onto card x of this stack >End if > >End preopenstack > > > > >_______________________________________________ >use-livecode mailing list >[email protected] >Please visit this url to subscribe, unsubscribe and manage your >subscription preferences: >http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
