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
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
On 3/23/12 1:09 AM, Bill Vlahos wrote:
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.
Trap the openStack message and see if the target is a
Bill-
Thursday, March 22, 2012, 8:56:14 PM, you wrote:
I'm trying to suppress openStack messages being sent. Lock messages doesn't
prevent it.
This script generates an openStack message. How can I prevent
that for the duration of the answer command?
on mouseUp
lock messages
Mark,
I want the dialog box to open but not send an openStack message.
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.
Bill Vlahos
Bill-
Thursday, March 22, 2012, 10:36:03 PM, you 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
