Easy enough to just click the suppress messages button before opening the
stack. You will probably want to keep messages suppressed in this situation if
going to other stacks and cards is going to trigger actions that the openstack
has not set up yet. You can make a handler called startApp or so
On 15.02.2013 at 17:56 Uhr +0100 Graham Samuel apparently wrote:
Another naive questions, but this hasn't happened to me before, or
at least I haven't recognised it properly.
I'm looking at some code written by an associate. As normal (to me)
it's a mainstack and a lot of substacks. I want to
Thanks Klaus. I guess I didn't encounter this because I always begin my apps
with a 'startUp' handler - these are not executed when a stack is loaded into
the IDE, but they are when a standalone is loaded. One can test the logic by
doing 'send "startUp" to...'. I do use preOpenCard handlers but
Hi Graham,
Am 15.02.2013 um 17:56 schrieb Graham Samuel :
> Another naive questions, but this hasn't happened to me before, or at least I
> haven't recognised it properly.
>
> I'm looking at some code written by an associate. As normal (to me) it's a
> mainstack and a lot of substacks. I want
Another naive questions, but this hasn't happened to me before, or at least I
haven't recognised it properly.
I'm looking at some code written by an associate. As normal (to me) it's a
mainstack and a lot of substacks. I want to tinker with the code, so I open the
mainstack in the LC IDE, and i
