tree view widget

Ali Lloyd ali.lloyd at
Mon May 16 11:41:30 EDT 2016

There were several fixes applied to the custom properties editor which is
very similar-it appears we (I) forgot to also apply them to the array
editor. This is very easily rectified. Sorry for any inconvenience.

On Sun, May 15, 2016 at 9:30 PM Dave Kilroy <dave at>

> Talk about buggy - my last posting had so many typos I'm doing it again:
> ------
> Yeah that inspector is buggy.
> I think the  'Key:' and 'Value:' properties are only for when you are using
> the inspector to add or update elements to it
> If you click the "+ Add new element" button at the top of the 'Arraydata'
> property field, then highlight the new key in the 'Arraydata' field, then
> click in the 'Value:' field and write something followed by pressing the
> tab
> or return key then the value will appear in 'Arraydata'.
> But quite a lot of the time the 'Key:' field is of no use (the hilited key
> in the 'Arraydata' field always seems to over-ride anything in the 'Key:'
> field). And the inspector seems to be unable to accept data for
> multi-dimensional arrays.
> Much easier to use script to populate the widget's arrayData property.
> One other thing to note is that the hilitedElement returns the key with a
> trailing comma so in script I have to do something like:
>     put the hilitedElement of me into tKey
>     if char -1 of tKey is comma then delete char -1 of tKey
> -----
> "The first 90% of the task takes 90% of the time, and the last 10% takes
> the other 90% of the time."
> Peter M. Brigham
> --
> View this message in context:
> Sent from the Revolution - User mailing list archive at
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the Use-livecode mailing list