are others like parentDocument you can use in custom MXML components. And
of course in custom components built using AS3 there's the Application.application.*
reference available after importing mx.core.Application.
| Aaron West
| aaron AT trajiklyhip DOT com
| http://www.trajiklyhip.com/blog/
| Certified Advanced Adobe ColdFusion MX 7 Developer
| Certified Macromedia FlashMX Developer
| Adobe Community Expert
On Oct 18, 2006, at 11:39 PM, Iko Knyphausen wrote:
Finally figured it out: It was a scope problem. <mx:component> has its own scope which explains why nothing beyond your parents (editor host) “data” object is visible. If you want to use an inline itemEditor that is data bound to other dynamic sources than the hosting component’s dataProvider, such as an XML for example, you just use the “outerDocument” keyword as a prefix. The following is an example for an inline itemEditor combobox that gets its own data independently from the host.... (hope this helps someone to learn faster than me ;-) )
<x-tad-bigger> <mx:Component id="inlineEditor"></x-tad-bigger>
<x-tad-bigger><mx:ComboBox labelField="lastName" dataProvider="{</x-tad-bigger><x-tad-bigger>outerDocument</x-tad-bigger><x-tad-bigger>.userInfo.lastResult.users.user}"/></x-tad-bigger>
<x-tad-bigger> </mx:Component> </x-tad-bigger>
