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

[Pete]

I hate using the long ID.  The development and live versions of my
behaviors are in two different stack files so dev work doesn't cause
problems with live work.  If I used the long form of the behavior
references, I'd have to go and change all of them every time I put a new
version of an application into the live environment.  Using the stackFiles
to fully dereference the behavior stack name means I only have to change
the stackfiles setting to point to a different behavior stack file and I'm
done.

On Tue, Dec 27, 2011 at 12:05 PM, Bob Sneidar <bobs at twft.com> wrote:

> Good point. The proper syntax *should* be
> set the behavior of <object> to the long id of button <the button object>.
> If the behavior script button is located on the first card of the stack the
> object is in, then you can use shorter versions, but why risk it? In your
> case, since the behavior is in a library, use the long ID.
>
> Bob
>
>
> On Dec 27, 2011, at 11:23 AM, Pete wrote:
>
> > OK, not exactly the same issue I had but stackfiles might still help.  If
> > your behaviors don't use a fully qualified stack file name (eg button id
> > 1020 of stack "Behaviors"), a stackfiles entry naming Behaviors and its
> > fully qualified stackfile path enables LC to resolve the behavior
> > references.  Not sure if that's your situation but maybe that will help.
> > Pete
> >
> > On Tue, Dec 27, 2011 at 10:47 AM, Todd Geist <todd at geistinteractive.com
> >wrote:
> >
> >> They are in the Library Stack itself not a substack.
> >>
> >> So you essentially injected the Library stack into the Main stack?
> >>
> >> On Tue, Dec 27, 2011 at 10:39 AM, Pete <pete at mollysrevenge.com> wrote:
> >>
> >>> 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
> >>>
> >>
> >> 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>
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> 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>