--- In flexcoders@yahoogroups.com, "gmoniey22" <gmonie...@...> wrote: > > Thanks for the reply...I come from a Java background, so creating a custom > component is not "scary" so to speak...I was just hoping there may be an > easier way to do it directly to the TabNavigator instance. > > Also, out of curiosity, why do you not recommend the spacer? >
When I said it would be "scary" all I was saying was that sometimes it can take a long time to set up exactly as needed. I did not mean to offend you in any way. I don't like the spacer idea mainly because it's a 3'rd party, with it's own width or height, I don't see the need for it, not here anyway. If that (extending component) is not the wanted approach you can always try the absolute positioning. I would recommend something like this <?xml version="1.0"?> <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"; > <mx:Canvas width="100%" height="100%"> <mx:TabNavigator id="tabN" width="100%" height="100%" updateComplete="textI.setStyle('left',tabN.getTabAt(tabN.numChildren-1).x+tabN.getTabAt(tabN.numChildren-1).width)" > <mx:VBox > </mx:VBox> <mx:VBox > </mx:VBox> <mx:VBox > </mx:VBox> </mx:TabNavigator> <mx:TextInput id="textI" /> </mx:Canvas> </mx:Application> So that is textI.setStyle('left',tabN.getTabAt(tabN.numChildren-1).x+tabN.getTabAt(tabN.numChildren-1).width) Setting it on the update complete of the tabnavigator and not on the creationcomplete of the textinput. This way you take into account any resize that might happen the id on the tabNavigator can be removed and tabN inside the setStyle() can be substituted with event.target or event.currentTarget
