Synchronicity

Peter Haworth pete at lcsql.com
Mon Jan 28 11:30:17 CST 2013


Thanks to all for the input.

I abandoned trying to use the visibility of the group as the flag to stop
processing, just couldn't seem to get that working.

Using a custom property as the flag now works. Turned out I needed to check
the cprop in a couple of lower level handlers which I had forgotten to
consider.

Pete
lcSQL Software <http://www.lcsql.com>


On Mon, Jan 28, 2013 at 5:05 AM, Thomas McGrath III <mcgrath3 at mac.com>wrote:

> Peter,
>
> Sometimes when I am debugging through a handler, it seems to me, that
> visible states do not always happen when I think they should. But they work
> fine during normal running of the script.
>
> Also, I find it best to use a flag type check set when the item is hidden
> rather than checking the 'live' state of the vis of the object.
>
> Lastly, sometimes when I am not getting an exit top (exit to top) to
> respond correctly I throw everything that will be exited into a separate
> handler that I send in time to, giving the smallest handler that sends to
> it time to complete itself and then the sent handler can be exited.
>
> Just some thoughts to think on, not sure if they will help.
>
> Tom
>
> Sent from my iPad
>
> On Jan 27, 2013, at 8:48 PM, Peter Haworth <pete at lcsql.com> wrote:
>
> > At various points throughout the processing, I check if the group is
> > visible and if so, I exit all the way out of the process - tried exit top
> > and cascading exits up the handler chain.  Didn't work.  Also, when I try
> > to check this out by stepping though with debug, the group is still
> visible
> > on the screen long after the hide command has been issued.
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>


More information about the use-livecode mailing list