I have a custom component “A” which implements a DisabledBead in ActionScript. 
It has a getter called “enabled”.

I have another MXML file “B” which uses the component and specifies 

I’m assuming the “enabled” property in “A” will be renamed without an @export.

The mxml in “B” will still be using a string for the property name which will 
be “enabled” that will be undefined.

> On Aug 9, 2017, at 7:55 AM, Alex Harui <aha...@adobe.com.INVALID> wrote:
> I just tried DataBindingExample.  MyInitialView is essentially a custom
> component.  What are you thinking won't work?
> -Alex
> On 8/8/17, 2:30 PM, "Harbs" <harbs.li...@gmail.com> wrote:
>> Did you try MXML with custom components? I’m not sure I understand how
>> that would work.
>>> On Aug 9, 2017, at 12:01 AM, Alex Harui <aha...@adobe.com.INVALID>
>>> wrote:
>>> Some things I found were that MXML isn't a problem because the id maps
>>> to
>>> a getter/setter which maps to Object.DefineProperty which takes an
>>> object
>>> structure where the ids are keys so they don't get renamed.

Reply via email to