I have run into a similar thing before, triggering an openStack handler when I did not want to. I think the only real solution to what you are doing here is to test conditionally in your frontScript openstack handler for your particular conditions, and pass openStack messages when your conditions are not met. I don't think stopping openStack in a frontScript is a very good idea.
Bob On Mar 22, 2012, at 11:09 PM, Bill Vlahos wrote: > Mark, > > Yes I can. In fact, that is how I'm seeing it in the first place. I have an > openStack handler in the front script. My example script doesn't normally > generate an openStack message but LiveCode did. > > Thanks, > Bill > > On Mar 22, 2012, at 10:47 PM, Mark Wieder wrote: > >>> I'm writing a plugin for the LiveCode IDE that triggers when a >>> stack is opened. In the case of my own stack I don't want to trigger >>> it when all I'm doing is opening up a dialog box in my own plugin. >> >> Hmmm... can you catch openStack in a frontscript and check for the >> target there? > > _______________________________________________ > 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
