On Sun, Apr 17, 2016 at 1:25 PM, Sannyasin Brahmanathaswami <
bra...@hindu.org> wrote:
> On preopenStack
># assume the main stack the trigger this is still open
># but on Mobile the new stack will take over the screen
># where
>
so that the group can be updated:
if there is a group "
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
Tac
doch...@gmail.com> 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
On Sun, Apr 17, 2016 at 6:06 AM, AndyP wrote:
> You could just copy the group from a card in the main stack and paste it
> into
> the cards of the module stacks at open stack if the group does not already
> exist.
>
>
If you do this, though, you need an automated way to copy it when it
changes.
-Background-Group-Across-Multiple-Stacks-tp4703581p4703591.html
Sent from the Revolution - User mailing list archive at Nabble.com.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
This is a “How do you do it?” question as I’m sure many of have already solved
this in one or more ways.
Context: 1 main stack that has a group on the bottom which is the “tab-tool
bar” which is sent to background behavior and runs on the bottom of most
cards-screens in the app.
1 or more “Mo
