I never would have thought of that. What a handy tip.
On 7/22/2015 5:32 PM, Peter Haworth wrote:
Put a reference to the behavior stack in the stackFiles property of my
application stack and commented out the startup handler. It works!
On Wed, Jul 22, 2015 at 12:39 PM Peter Haworth <p...@lcsql.com> wrote:
Well now it's one of the ones that is assigned at startup - it wasn't when
I started this thread. I'm pretty sure this all has to do with the
engine's resolution of behavior references happening before all stacks are
loaded.
I have all my behaviors in a separate mainstack which is opened in a
preOpenCard handler of the stack whose controls reference the behaviors.
It appears even preOpenCard doesn't happen soon enough to allow the engine
to resolve the behavior references.
I wonder if putting a reference to the behaviors stack in the application
stack's stackFiles property would fix this. I will try and post the result.
On Wed, Jul 22, 2015 at 11:22 AM J. Landman Gay <jac...@hyperactivesw.com>
wrote:
Is this one of the behaviors that's dynamically assigned at startup or
when a stack opens? I wonder if it's assigned too soon, before
everything has finished loading.
On 7/22/2015 1:03 PM, Peter Haworth wrote:
Yep, checked it over and over, plus the spelling of the command. My
lcStackbrowser plugin has a feature where you click on an icon for an
object's behavior and it automatically opens its script - that opens the
correct script so pretty sure all is OK.
I tried dispatching to a different handler - same result.
I have got this to work however. I deleted the behavior reference and
reset it. After that, all works well again. But after quitting LC and
starting it again, the behavior is no longer resolved.
For some reason, the behavior is not being resolved at runtime by LC and
deleting and resetting it forces it to be resolved.
On Wed, Jul 22, 2015 at 9:57 AM J. Landman Gay <
jac...@hyperactivesw.com>
wrote:
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 <mwie...@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
ahsoftw...@gmail.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
