pete at lcsql.com
Wed Jul 22 07:45:12 CEST 2015
Yes, of course behavior is a property but the control referred to in the
behavior has a script and the loadData handler is in that script. Hope
that clarifies things
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:
More information about the use-livecode