On Mon, Dec 1, 2014 at 12:13 PM, Peter Haworth wrote:
> Good news is that your trick of resetting the behaviors to themselves
> fixed the problem! And it's really fast. Thanks for that.
I guess I spoke too soon.
Although the fix does work, controls with linked behaviors are now
misbehaving.
Hi Scott,
I stepped through my initialization code and it all goes through to the end
no matter which stack I open first.
Good news is that your trick of resetting the behaviors to themselves fixed
the problem! And it's really fast. Thanks for that.
I'm still not understanding why that should be
tion Services
> rdim...@evergreeninfo.net
>
> -Original Message-
> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On
> Behalf
> Of Peter Haworth
> Sent: Monday, December 01, 2014 1:32 PM
> To: How to use LiveCode
> Subject: Behaviors not behaving
Peter Haworth
Sent: Monday, December 01, 2014 1:32 PM
To: How to use LiveCode
Subject: Behaviors not behaving
I'm working on a system that consists of a plugin, a library stack file and
a stack file containing buttons with behavior scripts.
The plugin creates an application stack file pl
>From what you describe, there may be a timing thing going on as you suggest
>(controls opening before their behaviors are available). You say your plugin
>“creates an application stack file” so another thing to check is correct
>behavior references applied to your controls.
If your behaviors
I'm working on a system that consists of a plugin, a library stack file and
a stack file containing buttons with behavior scripts.
The plugin creates an application stack file plus various controls within
it that have their behaviors set to the buttons in the behavior stack file.
Since the behavi
