Strict Compile Mode

Peter Haworth pete at lcsql.com
Tue Oct 9 11:36:51 CDT 2012


Indeed!  Although recent frustrations have made me thing seriously about
using lock messages/wait a lot more even when there's no apparent reason
for doing so.

For example, with help from a kindly customer, I discovered that the
following line of code in a script:

"set the visible of stack tstackname to true"

... caused the rest of the script to not execute.  The fix was either to
move that line to the end of the script so there were no more lines to
execute after it or surround it with lock/unlock messages.  I've no doubt
there's a good explanation for that behavior but what it could possibly be
escapes me.

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



On Tue, Oct 9, 2012 at 8:37 AM, Bob Sneidar <bobs at twft.com> wrote:

> I think he was joking.
>
> On Oct 9, 2012, at 4:53 AM, Peter M. Brigham wrote:
>
> > That's fine if you never use visual effects, since everything unlocks
> when the current handlers are done and the engine issues an idle message.
> But if you need visual transitions, scattering around lock screen commands
> is a nightmare -- I can't tell you how much time I've spend trying to chase
> down an obscure extra lock screen that breaks my visual effects.
> >
> > -- Peter
> >
> > Peter M. Brigham
> > pmbrig at gmail.com
> > http://home.comcast.net/~pmbrig
> >
> > On Oct 8, 2012, at 6:30 PM, Peter Haworth wrote:
> >
> >> I've pretty much decided that every handler should start with lock
> messages
> >> and lock screen...
> >
> >
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> 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