Yes, but Peter has a single behavior for all his cards, but unique script local
variables for each card. He wants those script local variables to be visible to
In a related note, I want to say again that properties can act as scoped
variables using the method I described. So
Bob Sneidar wrote:
> I did a quick little test. The card's script local variables are not
> accessible from the behavior script.
True, but you may not need to: each object subscribed to a behavior
script maintains its own set of script-local variables.
Thanks Bob, I’ll look at this more closely.
One benefit of using custom properties rather than local variables is that I’ve
seen that local variables are sometimes emptied on some script errors when
working on a script. Then I have to quit and reload the stack.
On Feb 23, 2017, at 3:17
I did a quick little test. The card's script local variables are not accessible
from the behavior script.
At this point you might consider using card properties instead. This is what I
have been doing. This way each card can have it's own "variables" in the form
of properties. Then you can
I may be mistaken, but I think that script locals are accessible to a behavior
script. If so, you could keep the script local variables in the card, and the
handlers in a library or backscript. I will set up a test for that.
> On Feb 23, 2017, at 14:51 , Peter Bogdanoff via
This is a good question. In my case, each card script has script local
variables that are used only for that card.
In this unusual case (I’m creating a text search method) I need to access the
contents of those variables from another stack.
I indeed would like to move common handlers to
> On Feb 23, 2017, at 12:32 PM, Peter Bogdanoff via use-livecode
> > wrote:
> put value("myFunction(hello, world)", group "myGroup" of card "myCard") into
> I want to use a variable as a parameter instead of
When I encounter situations like these, I begin to ask myself why the handler
is in a card script. If it needs to be accessible from other cards, it should
probably be moved to the stack script, or put into a button and inserted into
front or back. I have 3 buttons I use for this effect:
Yes, thank you, that works. I used:
dispatch function "getPageNumber" to card "MITA" of stack "MITA" with tID
What came back was in “the result”
“it” contained “handled”
On Feb 23, 2017, at 12:54 PM, Mike Bonner via use-livecode
> Will this work for
Will this work for you?
dispatch function "myFunction" to card "myCard"
put the result into tResult
Parameters can also be passed using the "with" extension. Unlike the
"call", "send" and "value" handlers, the parameters are sent directly to
the target handler, rather than being extracted from
Mail list logo