As per my last post regarding IMXMLObject I noticed a few incoonsistancies and was wondering if anyone else had come across these; or if anyone at Adobe waas aware of these and had a workaround / reason it behaves in this manner.
For those who have not read my initial post, I was looking at IMXMLObject for the creation of truly bespoke MXML components. In doing so a few issues arose.
It appears that if you switch to design view it errors about the root item being undeclared.
An unknown item is declared as the root of your MXML document. Switch to source mode to correct it.
New > MXML Component
If you chose New > MXML Component. There is a drop down that allows you to chose the component you want to extend your component from. To my mind if you can create a bespoke component via IMXMLObject it would have made more sense to add the option of Object, or IMXMLObject even :p, from the dropdown and have the code generate from that. I can understand why it isn’t in there. However it does limit the usefulness of the new MXML Component option to that of just components extended from UIComponent – which, as it happens means any components in the project you have extended from UIComponent or below.
It’s a minor thing but it would have been nice to keep them all together.