How/When are behavior references resolved?

[Pete]

Great idea, I just added my 5 votes for it.

This thing is driving me crazy and will affect the livecode tv presentation
I'm doing later this morning.  Not insurmountable, just means restarting LC
when I shouldn't need to.
Pete
Molly's Revenge <http://www.mollysrevenge.com>




On Sat, Jul 16, 2011 at 8:16 AM, Richard Gaskin
<ambassador at fourthworld.com>wrote:

> Behaviors are very powerful, but also very picky about how and when they're
> initially resolved.  If you don't architect just so, they will not be
> resolved correctly and your code won't work.
>
> I've submitted a request which would give developer much greater
> flexibility and minimal cost to RunRev:
>
> Add "resolve behaviors" command
> <http://quality.runrev.com/**show_bug.cgi?id=8993<http://quality.runrev.com/show_bug.cgi?id=8993>
> >
>
> The idea here is that when the proposed "resolve behaviors" command is
> called, it merely triggers the existing code in the engine which resolves
> behavior references.   This would be exactly as what happens when a stack is
> first loaded, but by being able to invoke resolution at any time the
> developer has much more flexibility with WHEN that resolution happens,
> fixing a good many initialization issues developers experience with
> behaviors.
>
> --
>  Richard Gaskin
>  Fourth World
>  LiveCode training and consulting: http://www.fourthworld.com
>  Webzine for LiveCode developers: http://www.LiveCodeJournal.com
>  LiveCode Journal blog: http://LiveCodejournal.com/**blog.irv<http://LiveCodejournal.com/blog.irv>
>
>
> ______________________________**_________________
> 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<http://lists.runrev.com/mailman/listinfo/use-livecode>
>
>