Quick follow-up. It turns out that the Exclude met...

2008-07-23T21:44:00.000-04:00

Quick follow-up. It turns out that the Exclude metadata tag does even less than I thought it does. All it does is make it so the excluded property will not show up in the code hinting list. You can still use the property, even within the tag declaring that component that it is a property of. So, continuing the example from my previous comments, it will work just fine to do the following:

<myNamespace:MyComponent id=”myComponent” alpha=“ 0.5” />

Gordon actually says this in his original post, but I did not understand what he meant.

Although everything said above seems correct, I fo...

2008-07-23T21:27:00.000-04:00

Although everything said above seems correct, I found it a bit confusing. Based on some testing, here is my understanding of how the Exclude metadata tag works, at least for properties (I haven't tested anything else).

Let's say that we have a custom component in the file MyComponent.mxml, and within MyComponent.mxml, we have something like

<mx:Metadata>
[Exclude(name="alpha", kind="property")]
</mx:Metadata>

Then within another MXML component, we instantiate our custom component as follows:

<myNamespace:MyComponent id="myComponent" />

Because of the Exclude tag set for the alpha property, we will not be able to have an alpha attribute within the above tag declaring MyComponent.

However, that is the only thing limited by the exclude tag. We will still be able to access the alpha property of the myComponent object, both for setting and getting by ActionScript, and for binding within another MXML tag.

Comments on The Flex Non-Docs: metadata.Exclude

Quick follow-up. It turns out that the Exclude met...

Although everything said above seems correct, I fo...