the target

[Peter Haworth]

I think you'll need to use the long name/ID of the button not just the name
or the stack you go to will try to find the button on itself instead of on
the original stack.

Couple of other alternatives since I try to avoid global variables whenever
possible.  The dialogData is a good way to pass information between stacks.
 In your mouseUp handler:

set the dialogData to the long ID of me

Then in the stack you go to, you can put the dialogData into a variable to
get the button name.

Another way would be to set a custom property of the destination stack to
the long ID of the button (before you go to it of course :-).


Pete
lcSQL Software <http://www.lcsql.com>



On Sat, Sep 15, 2012 at 5:57 PM, Mark Smith <Mark_Smith at cpe.umanitoba.ca>wrote:

> Ok, thanks Mike and Pete. I understand what is going on now. So I guess the
> best (and only?) way to keep track of this is:
>
> on mouseup
>    stuff the name of the button in a global variable
>    go stack test
>
> then in "test" retrieve the button name from the global variable.
> Doesn't sound too complicated but I was trying to see if there was a
> cleaner
> way than using a global.
>
> Cheers,
>
> -- Mark
>
>
>
>
> --
> View this message in context:
> http://runtime-revolution.278305.n4.nabble.com/the-target-tp4655052p4655055.html
> Sent from the Revolution - User mailing list archive at Nabble.com.
>
> _______________________________________________
> 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
>