J. Landman Gay
jacque at hyperactivesw.com
Wed Jul 22 12:57:08 EDT 2015
You double-checked the path to the behavior, right? If there are any
other handlers in the behavior, do those work?
On 7/22/2015 12:48 AM, Peter Haworth wrote:
> Right, the unhandled is what is throwing me, plus the fact that using send
> results in a runtime error.
> As I've found, what I'm doing works in a simplified environment so for some
> reason, this particular behavior isn't being resolved, just can't figure
> out why.
> On Tue, Jul 21, 2015 at 8:44 PM Mark Wieder <mwieder at ahsoftware.net> wrote:
>> On 07/21/2015 04:55 PM, Peter Haworth wrote:
>>> I just tried a very simple test in another stack and it worked so there
>>> must be something in the stack with the problem that is preventing the
>>> behavior from being resolved.
>> Well, it *should* work. In most cases anyway.
>> The only thing I can think of that would mess it up is if you have a
>> loadData handler somewhere in a frontscript and it isn't passing the
>> message on when it's done.
>> I think of behavior scripts as private backscripts of the parent object.
>> So it should be the next thing in the message path unless a frontscript
>> grabs the message first and never lets go.
>> I don't think that explains the "unhandled" status though, so there may
>> be something else going on.
>> Mark Wieder
>> ahsoftware at gmail.com
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
More information about the Use-livecode