For what you are doing, I suspect it is the underlying details about what the 
properties are and their 'meta' attributes which are really needed.

There are functions in the LC8 IDE for getting thins information for all 
controls - using the metadata file which accompanies any widget - however, we 
really need to document them :)

What approach did you take in the end?

Mark.

Sent from my iPhone

> On 14 Oct 2015, at 18:33, Peter Haworth <p...@lcsql.com> wrote:
> 
> Would be great if that were the case and maybe it will be eventually but
> when I tried "get the keys of widget 1 of this card", I got an empty array.
> 
> Widgets have their own set of properties which are defined as part of the
> process of creating them. You get and set them as any other property but
> lcStackbrowser needs to discover their names. They're somewhat akin to
> custom properties in my mind but they don't show up as such in the IDE.
> 
> Pete
> lcSQL Software <http://www.lcsql.com>
> Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
> SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>
> 
> On Wed, Oct 14, 2015 at 10:07 AM, Richard Gaskin <ambassa...@fourthworld.com
>> wrote:
> 
>> Peter Haworth wrote:
>> 
>>> New version of lcStackBrowser coming out this week with Widget support.
>>> Not super difficult but did involve some searching around to figure out
>>> how
>>> to get the properties of a widget.
>> 
>> If Widgets are a means of adding new objects to LC Script to compliment
>> the existing ones, wouldn't "the properties" work as it always has?
>> 
>> --
>> Richard Gaskin
>> Fourth World Systems
>> Software Design and Development for the Desktop, Mobile, and the Web
>> ____________________________________________________________________
>> ambassa...@fourthworld.com                http://www.FourthWorld.com
>> 
>> 
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode@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@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to