Paul… great! that works. tks is that documented somewhere? Semi-unintuitive.. but I guess is also makes sense… UX decision… build some horrible long cascading menu with all buttons on all cards (as behavior options) or … leave the inspector of open and *then* navigate to your behaviors card.
On 5/25/16, 9:29 AM, "use-livecode on behalf of Paul Hibbert" <use-livecode-boun...@lists.runrev.com on behalf of p...@livecode.org> wrote: >Try this: > >Go to card 2 >Open the Project Browser and expand the view for card 1 >Right click on the target button of card 1 in the PB and choose ‘Property >Inspector’ >The PI for the button on card 1 will now allow you to link the behaviour to >the button on cards 2 > >HTH > >Paul _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
