That post from Ali says they are not available; it doesn’t say they should be 
not available.

I’d say they should be -  Ali’s workaround is good for the IDE only.

So no reason not to submit as a bug/request, and get a proper determination 
from LCLtd.

Alex

Sent from my iPad

> On 6 Apr 2022, at 13:37, matthias rebbe via use-livecode 
> <use-livecode@lists.runrev.com> wrote:
> 
> That is not available according to this post from Ali Lloyd
> 
> https://forums.livecode.com/viewtopic.php?t=27183#p141945 
> <https://forums.livecode.com/viewtopic.php?t=27183#p141945>
> 
> 
>> Am 06.04.2022 um 14:03 schrieb Neville Smythe via use-livecode 
>> <use-livecode@lists.runrev.com>:
>> 
>> Is it not a bug that
>> 
>>    the properties of widget “foo”
>> 
>> returns empty (for all values of foo)?
>> 
>> No rect, no visible, no disabled etc, even though these clearly are settable 
>> and functional properties of the widget.
>> 
>> You can
>> 
>>   export widget “foo” to array “bar”
>> 
>> but that gives the intrinsic properties of the widget not the usual object 
>> properties. Oh and don’t forget the reserved word “array” in the above line, 
>> that causes an IDE crash (bug 23655 
>> <https://quality.livecode.com/show_bug.cgi?id=23655> confirmed)
>> 
>> Neville
>> _______________________________________________
>> 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