Feedback request: getProp/setProp and lockMessages

dunbarx at aol.com dunbarx at aol.com
Sat Nov 23 11:22:26 EST 2013


I agree with the concept that the world of set and getProp messages lives almost entirely in scripts, not embedded in the underlying "engine". Being therefore "hand-made", they should rightly be grouped, as Mark W. asserts, and as Richard so clearly explains, with its kindred "send", et. al.


Craig Newman



-----Original Message-----
From: Scott Rossi <scott at tactilemedia.com>
To: How to use LiveCode <use-livecode at lists.runrev.com>
Sent: Sat, Nov 23, 2013 11:00 am
Subject: Re: Feedback request:  getProp/setProp and lockMessages


Yes, please.  Two thumbs up. +10

In my projects, I've been using a combination of custom properties and functions 
to get around the locked messages limitation, so this change would be a welcome 
addition.

Regards,

Scott Rossi
Creative Director
Tactile Media, UX Design

> On Nov 23, 2013, at 7:34 AM, Richard Gaskin <ambassador at fourthworld.com> 
wrote:
> 
> Make getProp and setProp immune to lockMessages

_______________________________________________
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