Hi Pete: Not sure if this is true in your case, but one reason why this can sometimes happen is if, for whatever reason, a control that has a behavior assigned to it gets opened before is associated behavior is present in memory. You might check if there is any delay occurring when launching the library stack.
You can usually get around this without exiting LiveCode by using a script to set a control's behavior to the same behavior reference. You can also try setting the control's behavior to empty first. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 9/24/14 3:46 PM, "Peter Haworth" <[email protected]> wrote: >I'm working with lots of controls that have behaviors. The behavior >buttons are all in a library stack. All works fine most of the time but >every now and again, none of the behavior scripts are executed (as >verified >with breakpoints at the start of them). The message box shows the library >stack is still in use and the behavior properties all look valid > >I can't pin down exactly what causes this but I think that editing a lot >of >the behavior scripts might cause this, but I'm pretty sure that shouldn't >happen. When it happens, the only way to get the behaviors to work again >is >to quit LC and run again. > >Anyone else's applications' guilty of bad behavior like this and if so is >there a way to correct their behavior? > >Pete >lcSQL Software <http://www.lcsql.com> >Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and >SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> >_______________________________________________ >use-livecode mailing list >[email protected] >Please visit this url to subscribe, unsubscribe and manage your >subscription preferences: >http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
