Np, and if you want to prevent openStack and openCard messages in the destination stack from firing, remember to lock messages before going to and from the stack, and unlock them before terminating the script. I have not tested that so I do not know what hidden consequences there may be. In other words, use at your own risk. ;-)
Bob On Nov 23, 2011, at 10:24 AM, Pete wrote: > My apologies to Mark - the lock messages/screen didn't fix the problem > after all - confusion on my part. > > Thanks Bob, your solution does what I want. > > Pete > > On Tue, Nov 22, 2011 at 4:45 PM, Bob Sneidar <b...@twft.com> wrote: > >> I do not believe there is a way to prevent it from opening, but you can >> copy the card, go to the destination stack invisible and paste the card. >> Then go back to the source stack. Would that help? >> >> I tried this in a button and it worked famously: >> >> on mouseUp pMouseBtnNo >> copy card 1 of stack "Untitled 1" >> go invisible to stack "Untitled 2" >> paste >> go stack "Untitled 1" >> end mouseUp >> >> Bob _______________________________________________ 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
