Nope, i changed the creation policy to all and it still fails. Any other ideas? Please, if you haven't tried the sample code that i posted, please try it so you can see the behavior by yourself.
It is of no help to post a possible solution if you haven't reproduced the bug. It is not a very complicated test code, so please try it out. Thanks --- In [email protected], "Tracy Spratt" <[EMAIL PROTECTED]> wrote: > > In your TabNavigator, set creationPolicy="all", and re-run your test. > If that changes the behavior, let us know. > > Tracy > > -----Original Message----- > From: [email protected] > [mailto:[EMAIL PROTECTED] On Behalf Of dmiramontesval > Sent: Wednesday, December 27, 2006 6:55 PM > To: [email protected] > Subject: [flexcomponents] Re: Custom Components Bug > > No idea what you mean, i posted an example so you can check it out. > Try it and if the solution is that deferred thing you said, please let > me know how to fix it > > --- In [email protected], "Tracy Spratt" <tspratt@> > wrote: > > > > This sounds like the deferred instantiation issue. Have you checked > > that? > > > > If you don't know what I mean, post back. > > > > Tracy > > > > -----Original Message----- > > From: [email protected] > > [mailto:[EMAIL PROTECTED] On Behalf Of dmiramontesval > > Sent: Wednesday, December 27, 2006 5:21 PM > > To: [email protected] > > Subject: [flexcomponents] Re: Custom Components Bug > > > > I forgot an important detail and now that i tested it i kinda know why > > it fails. > > > > The TabNavigator is also a custom TabNavigator, and when using it is > > when the bug appears, if i use the normal TabNavigator then it works. > > I also noticed that if i use the custom TabNavigator every property > > that i try to set in the custom component fails. > > > > Why is that? there is nothing weird with my custom TabNavigator, i > > only added code to handle an custom event i dispatch. > > > > > > > > > > --- In [email protected], "dmiramontesval" > > <dmiramontesval@> wrote: > > > > > > I have a little issue when using custom components and localization. > I > > > have a TabNavigator component, which has as children some custom > > > components which are containers: > > > > > > <mx:TabNavigator> > > > <custom:MyContainer/> > > > </mx:TabNavigator> > > > > > > > > > MyContainer: > > > > > > <mx:HBox> > > > <mx:DataGrid/> > > > <mx:Label/> > > > </mx:HBox> > > > > > > The bug appears when i want to set the label property like this: > > > > > > <mx:TabNavigator> > > > <custom:MyContainer id="myC" > label="{resource.getString('hello')}"/> > > > </mx:TabNavigator> > > > > > > <mx:Script> > > > <![CDATA[ > > > import mx.resources.ResourceBundle; > > > > > > [ResourceBundle("PersonaFlex")] > > > private static var resource : ResourceBundle; > > > > > > ]]> > > > </mx:Script> > > > > > > If i test my application the label on the tab appears empty, as if i > > > didn't set the label property. As you can see i am using a > > > localization file. > > > The funny thing is that if i do this: > > > > > > <mx:TabNavigator> > > > <custom:MyContainer id="myC" > label="{resource.getString('hello')}"/> > > > <mx:HBox label="{resource.getString('hello')}"/> > > > </mx:TabNavigator> > > > > > > the second tab label does appear but the first one still appears > > emtpy. > > > Furthermore, if i set the label inside my custom component instead > of > > > doing it in the tabNavigator like this: > > > > > > <mx:TabNavigator> > > > <custom:MyContainer id="myC"/> > > > <mx:HBox label="{resource.getString('hello')}"/> > > > </mx:TabNavigator> > > > > > > > > > MyContainer: > > > > > > <mx:HBox label="{resource.getString('hello')}"> > > > <mx:DataGrid/> > > > <mx:Label/> > > > </mx:HBox> > > > > > > This one works, both tabs' labels appear. > > > > > > So why is this happening? Why can't i set the label property of a > > > custom container from the main application? Why if i set it to a > > > non-custom component does work? > > > > > > Thanks > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > Yahoo! Groups Links >
