Unpopularity of global variables - why?

Scott Rossi scott at tactilemedia.com
Mon Oct 15 18:39:07 CDT 2012


Bob, I always need access to setting of properties, custom or otherwise,
when making changes to objects.  Don't you?  I don't think it should
matter whether messages are locked and/or the screen is locked.

Regarding data grids, I'm not sure what you mean.  You can get into a data
grid group the same way you do any other group -- with the data grid
selected, press the Edit Group button or script "start editing grp
"datagrid 1".

And in case you haven't come across this before, data grids are subject to
the same limitations as any other control when it comes to custom
properties and locked messages -- see the 3rd item on this page:
What Sorts of Things Should I Not Do In Order To Avoid Needless Suffering?
http://tinyurl.com/8n97xw6


In my custom control products, I've taken to supplementing every
settable/readable property with a custom property set so folks can access
control values even when messages are locked, due to the locked messages
limitation.  Life would be better/easier if I didn't have to do this.

Regards,

Scott Rossi
Creative Director
Tactile Media, UX Design




On 10/15/12 4:08 PM, "Bob Sneidar" <bobs at twft.com> wrote:

>Do you still need custom props in this scenario? Also, complex groups got
>me thinking, LC does not include Datagrids when using edit group or
>select group. That is curious. They are obviously doing something
>different. Is it something the IDE just "knows" or is there some kind of
>property, or custom props set up in the datagrid library that allows them
>to work like that? If the latter, I wonder if that will work for other
>groups as well? I know you make great use of groups in a lot of your
>work. 
>
>Bob
>
>
>On Oct 15, 2012, at 3:53 PM, Scott Rossi wrote:
>
>> One situation in particular is when you make changes to numerous objects
>> via a single script, such as grouping, changing location, scaling, etc.
>> These cases will almost always execute faster when lock messages is true
>> because the IDE (and/or scripts that track objects and their properties)
>> won't update until messages are unlocked.  Locking the screen helps, but
>> locking messages helps more.
>> 
>> Regards,
>> 
>> Scott Rossi
>> Creative Director
>> Tactile Media, UX Design
>> 
>> 
>> 
>> 
>> On 10/15/12 3:38 PM, "Bob Sneidar" <bobs at twft.com> wrote:
>> 
>>> I'd be curious if people can summarize all the times that locking
>>> messages became a necessity, and then see if some of us can figure out
>>> "another way of going about it".
>> 
>> 
>> 
>> _______________________________________________
>> 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