I just implemented by first use of nested behaviors. Marvelous!
But it occurred to me right away, that I could use variables which were
"local", in the sense that their scope was within the context of the nested
arrays. Of course needed to declare the inside the behavior, otherwise you get
confused, but they are no globals.
I have nested "behavior_ListenUI"
# a generic UI that words of several cards
# inside
behavior_MyAudio
# just for this one card.
# On this card I am forced to use local set up "silly handlers"
local sDownloadedAudioA
on passAudioSelection pLine,pTitle
startPlayer sDownloadedAudioA[pLine][localURL],pTitle
end passAudioSelection
# because the startPlayer behavior is on the "generic" "behavior_ListenUI"
but if "sDownloadAudioA" was available to "behavior_ListenUI"
I won't need to passAudioSelection pLine,pTitle
instead, I just declare the
semi-local sDownloadedAudioA
on the mouseup handler it to a straight
startPlayer sDownloadedAudioA[pLine][localURL],pTitle
behavior_ListenUI
I hope that makes sense… if could post the entire scripts if it doesn’t .
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
