I meant “does” To get what you want (if different than above) would require something defined within each widget to export the desired internal information. One other thing that could be done is to extend the export to include everything that the engine knows about the widget (i.e. add the properties array to it).
Thanks, Brian On Sat, Feb 24, 2018 at 10:12 AM Brian Milby <br...@milby7.com> wrote: > Doe this get what you want: > export widget to array arrayVar > On Sat, Feb 24, 2018 at 10:01 AM Richard Gaskin via use-livecode < > email@example.com> wrote: > >> When we query the properties of any object, we get an array that lets us >> understand and even reproduce that object easily. >> >> Except with widgets. >> >> When we query the properties of a widget we get only the subset of >> properties common to all widgets, but none of the properties unique to >> any given widget type. >> >> Should the widget spec be enhanced to map its unique properties to be >> included among "the properties" array? >> >> -- >> Richard Gaskin >> Fourth World Systems >> >> _______________________________________________ >> use-livecode mailing list >> firstname.lastname@example.org >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode >> > _______________________________________________ use-livecode mailing list email@example.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode