Unpopularity of global variables - why?
bobs at twft.com
Mon Oct 15 16:47:54 EDT 2012
No it's my understanding that customKeys are the names of all your custom properties of a particular object. customProperties is an array with the name of the custom property as the key. So if you wanted to get the values of all your custom properties but you script is blind as to what exactly they are, you would first get the customKeys, then the customProperties, then loop through the lines of that and get each property by key name eg.
put the customKeys of this card into theKeys
put the customProperties of this card into aProps
repeat for each line theKey in theKeys
put aProps[theKey] into theCurrentKeyValue
-- do stuff with it.
On Oct 15, 2012, at 1:15 PM, Timothy Miller wrote:
> On Oct 15, 2012, at 12:21 PM, Richard Gaskin wrote:
>> Ken Ray wrote:
>>> Custom Props:
>>> Cons: *Much* easier to accidentally store permanently what
>>> should be a temporary change to a value (for stacks that need to call
>>> "save" for any reason); more difficult to use (gMyGlobal vs. "the
>>> uWidgetType of btn 3 of card 123 of stack 'WhoTheHellCares'")
> What's the difference between customKey and customProperty?
> Having read the dictionary, I now know less about it than I did before. Could it be that a customProperty is an array, whereas a customKey is a value, or list of values?
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode