Thanks for the idea Scott, hadn't thought of that. However, I checked my Plugins folder and the library stack is not in there so don't think that's the cause.
If I could only get the executionContexts somehow when the stack opened, I'd know what was going on. It's almost as if lockMessages is set true when the stack is opened. Pete lcSQL Software <http://www.lcsql.com> Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> On Sun, Nov 30, 2014 at 10:12 AM, Scott Rossi <sc...@tactilemedia.com> wrote: > You say the stack is opened as a library by a separate plugin stack. > > Is it possible you (inadvertently) assigned plugin settings to the library > itself, independently of the plugin? From your description of the > situation, that seems to be most likely. > > Regards, > > Scott Rossi > Creative Director > Tactile Media, UX Design > > > On Nov 30, 2014, at 9:59 AM, Peter Haworth <p...@lcsql.com> wrote: > > > > I'm trying to track down a strange situation where one of my stacks is > > being opened automatically when LC starts up. The stack is normally > opened > > as a library stack from a plugin but the plugin is set to open when I > > select it from the Plugins menu, not at startup, I've verified that the > > plugin is not in memory, plus the stack is not listed in the message box > > Stacks In Use tab. > > _______________________________________________ > 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
