Case Study: Behaviors Failing - Can't set break points

Pete pete at mollysrevenge.com
Tue Dec 27 12:39:37 CST 2011


Are the behavior buttons in the actual library stack or in a substack of
the library stack?  I've run into a similar problem before and ending
setting thew stackFiles property of the app's main stack to name the
behavior stack.
Pete

On Tue, Dec 27, 2011 at 10:23 AM, Todd Geist <todd at geistinteractive.com>wrote:

> On Tue, Dec 27, 2011 at 10:14 AM, Bob Sneidar <bobs at twft.com> wrote:
>
> > Where are the behavior buttons located? They have to be in the open stack
> > or *AN* open stack. I may be mistaken about this, but I think I am not. I
> > have a behavior button on the first card of an app stack, and all my
> > behaviors work fine there. They should also work if they are on the first
> > card of any stack you start using. Someone who knows more should correct
> me
> > if I am wrong.
> >
>
> The behaviors are in a library stack.  That stack was being loaded by the
> Main stack, in a PreOpenCard handler. the Main stack was also using the
> behaviors.  They are two separate stacks.
>
> So the Main stack loads into memory, then On PreOpenCard it loads the
> Library stack that has the behaviors.  This is the problem.  If the library
> stack is loaded first into memory, everything works.  So I may need a
> launcher file that Loads the Libraries first THEN the main stack.
>
> Todd
> _______________________________________________
> 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
>
>


-- 
Pete
Molly's Revenge <http://www.mollysrevenge.com>


More information about the use-livecode mailing list