TabNavigator.selectedIndex problem

What I'm trying to do, is some data validation before allowing a user to change tabs, so I put some code in the change handler on the tabNavigator, which fires when a user clicks another tab. If the validation fails, then the code sets the selectedIndex back to the index of the previous tab.
This all works fine, but for some reason, the tab which was clicked on becomes a "dead" tab, and no longer fires a change event when clicked on. Anyone know what is happening here, or a way to correct this issue?
I've tried tabNavigator.validateNow(), but that didn't seem to do much.
Many thanks!

Thanks for your input David. Basically, the client wants the app to check to make sure a user has entered certain data before allowing them to leave the current tab. The action the user takes, will be clicking on another tab, so the change event seems like the only place I can capture this action and alert the user they need to do something.
Here is an example of what the code looks like:
<?xml version="1.0" encoding="utf-8"?>
<mx:Application  xmlns:mx="http://www.adobe.com/2006/mxml">
     <mx:Script>
          <![CDATA[
          import  mx.events.FlexEvent;
          import  mx.events.IndexChangedEvent;
          protected function handleTnChange(e:Event):void
               var failed:Boolean = true;
               //Assume validation failed for test
               if (failed) {
                    tn.selectedIndex = _tnSelectedIndex; //tnSelectedIndex holds the previous selected tab index before the user click
               else{
                    //Proceed to the selected tab
     ]]>
     </mx:Script>
     <mx:TabNavigator  id="tn" change="handleTnChange(event)">
          <mx:Canvas label="Tab 1"  width="100%" height="100%">
          </mx:Canvas>
          <mx:Canvas label="Tab 2" width="100%" height="100%">
          </mx:Canvas>
          <mx:Canvas label="Tab 3" width="100%" height="100%">
          </mx:Canvas>
     </mx:TabNavigator>
</mx:Application>
So, assuming the user is on Tab 1, and clicks Tab 2, what is happening is the selectedIndex gets changed back to Tab 1 in the change function, but Tab 2 seems to become "dead", so that when the user clicks on Tab 2 again, it doesn't fire a change event.
Something I noticed while trying to figure out the problem, is that on the mouse down event when clicking a tab, the change fires, and the tab changes, but on the mouse up, the tabNavigator seems to come back, at least the tab itself, to the tab that was originally clicked before the selectedIndex was changed.
Anyway, hope this clears up what I'm trying to do.
Thanks!

Similar Messages

  • Tabnavigator selectedIndex issue

    I have a TabNavigator. The script controlling portion of it is:
                private function init():void{
                    tabNavBar.selectedIndex = 2;
    this works fine as the third tab is selected upon creationComplete of the component.
    However, if I send in an int via scripting, nothing changes.
                public function changeTab( e:FormEvent ):void {
                    Alert.show("Event value passed in is " + e.tabIndex.toString());           // Alerts Event value passed in is 0
                    Alert.show("Starting value is " + tabNavBar.selectedIndex.toString());  // Alerts starting value is -1 (no children??)
                    tabNavBar.selectedIndex = e.tabIndex;
                    Alert.show("Tab is now" + tabNavBar.selectedIndex.toString());          // Alerts Tab is now 0 (correct but doesn't change)
    Things I've tried:
    validateNow();
    int(e.tabIndex)
    e.tabIndex as int;
    Other suggestions?
    Thanks.

    Hi,
    the following code changes the tabnavigator programmatically, when you press the tabbar the change event then sets the tabnavigator to match . When you set the selected index it should just work, are you doing this from a popup window as that may have an effect on how the component updates(note: I'm using the latest sdk).
    you could try setting the update flag(this shouldn't really have any effect), tabnav.updateCompletePendingFlag=true; but without the full code its hard to say what the problem is.
    <?xml version="1.0" encoding="utf-8"?>
    <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
       xmlns:s="library://ns.adobe.com/flex/spark"
       xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600"
       creationComplete="application1_creationCompleteHandler(event)">
    <fx:Script>
    <![CDATA[
    import mx.collections.ArrayCollection;
    import mx.events.FlexEvent;
    import spark.events.IndexChangeEvent;
    [Bindable] private var myArr:ArrayCollection = new ArrayCollection(['1','2','3']);
    protected function application1_creationCompleteHandler(event:FlexEvent):void
    tabnav.selectedIndex = 1;
    protected function buttonbar1_changeHandler(event:IndexChangeEvent):void
    tabnav.selectedIndex = event.newIndex;
    ]]>
    </fx:Script>
    <fx:Declarations>
    <!-- Place non-visual elements (e.g., services, value objects) here -->
    </fx:Declarations>
    <mx:TabNavigator id="tabnav" x="174" y="191" width="579" height="254">
    <s:NavigatorContent label="Tab 1" width="100%" height="100%">
    </s:NavigatorContent>
    <s:NavigatorContent label="Tab 2" width="100%" height="100%">
    </s:NavigatorContent>
    <s:NavigatorContent label="Tab 3" width="100%" height="100%">
    </s:NavigatorContent>
    </mx:TabNavigator>
    <s:ButtonBar x="204" y="78" dataProvider="{myArr}" change="buttonbar1_changeHandler(event)"/>
    </s:Application>

  • TabNavigator selectedIndex not working

    I have reduced a problem I'm having to a very simple example.
    I'm using the routine in a validation of form, trying to make sure
    they don't leave the current tab index if a form is 'open.' It
    works the first time but after that, does not work every other
    time. Suggestions?

    I ran into a similar problem where the correct tab was not
    always being selected when the ViewStack selectedIndex changed.
    This is a bug in Flex, which I have reported and submitted a patch
    for.
    In the meantime, you can use the attached Custom Class, and
    this should fix your problem....

  • Accordion selectedIndex problem

    Hi everybody,
    I am trying to set my selectedIndex property to a certain value for my accordion upon click.
    Here is my code snippet
    public function changeItemClick():void{ 
    if(inboxView.inboxGrid.selectedIndex == -1 && (applicationVs.selectedIndex == 1)){
    applicationVs.selectedIndex = 0;
    Alert.show(
    "Please select a task " + String(applicationVs.selectedIndex));}
    <mx:Accordion 
    id="applicationVs" change="changeItemClick();" width="100%" height="100%" historyManagementEnabled="true" creationPolicy="all" >
    The problem is. when the functions are satisfied, the selectedIndex doesnt get assigned to 0 again.
    It stays at 1.
    Did anybody encounter such a problem? Could someone suggest a workaround. Please?
    Really appreciate your help
    Thank you
    Nikhil

    Did you search past threads? I thought someone had already solved this.

  • Tab Navigator Error

    Found a problem when submitting a textinput field from a
    canvas on a TabNavigator. Problem only occurs when you do not go to
    the tab when viewing on screen before submitting the TextInput.text
    This is the error.
    TypeError: Error #1009: Cannot access a property or method of
    a null object reference.
    If you click on the tab, view the contents of whatever and
    then submit, there is no error. If you do NOT click on the tab,
    then the error occurs. Seems like it does not create the tab until
    you view it. Which would not seem correct. Think of the case of
    entry screens where you have 3 or 4 or more tab sections on the
    screen.
    Thanks.
    Bill Brittain

    Hi Bill,
    > Found a problem when submitting a textinput field from a
    canvas on a
    > TabNavigator. Problem only occurs when you do not go to
    the tab when viewing
    > on screen before submitting the TextInput.text
    >
    > This is the error.
    > TypeError: Error #1009: Cannot access a property or
    method of a null object
    > reference.
    >
    > If you click on the tab, view the contents of whatever
    and then submit, there
    > is no error. If you do NOT click on the tab, then the
    error occurs. Seems
    > like it does not create the tab until you view it. Which
    would not seem
    > correct. Think of the case of entry screens where you
    have 3 or 4 or more tab
    > sections on the screen.
    Try setting creationPolicy="all" on the TabNavigator. By
    default,
    creationPolicy is set to "auto", which means the TabNavigator
    only
    creates the children of the initially visible pane on
    startup--this is
    to make startup faster. In your case, since you need to
    access children
    of the hidden tabs regardless of whether the user visits
    them, you
    should use creationPolicy="all".
    nj
    Flex Builder team

  • Module + Tab Navigator = Error

    Everything works FINE until I load a new module. (Even after
    I go back to the original module, I get the error). Any component
    with a Tab Container or Accordian throws the following error when I
    load the component:
    TypeError: Error #1009: Cannot access a property or method of
    a null object reference.
    at mx.managers::HistoryManager$/register()
    at mx.containers::ViewStack/::addedHandler()
    at flash.display::DisplayObjectContainer/addChildAt()
    at mx.core::UIComponent/
    http://www.adobe.com/2006/flex/mx/internal::$addChildAt()
    at mx.core::Container/addChildAt()
    at mx.core::Container/addChild()
    at mx.core::Container/createComponentFromDescriptor()
    at mx.core::Container/createComponentsFromDescriptors()
    at mx.core::Container/mx.core:Container::createChildren()
    at mx.core::UIComponent/initialize()
    I have turned off History manager in the compiler page of the
    project properties. That does not help any.
    Any suggestions?
    Thanks
    Bruce

    Hi Bill,
    > Found a problem when submitting a textinput field from a
    canvas on a
    > TabNavigator. Problem only occurs when you do not go to
    the tab when viewing
    > on screen before submitting the TextInput.text
    >
    > This is the error.
    > TypeError: Error #1009: Cannot access a property or
    method of a null object
    > reference.
    >
    > If you click on the tab, view the contents of whatever
    and then submit, there
    > is no error. If you do NOT click on the tab, then the
    error occurs. Seems
    > like it does not create the tab until you view it. Which
    would not seem
    > correct. Think of the case of entry screens where you
    have 3 or 4 or more tab
    > sections on the screen.
    Try setting creationPolicy="all" on the TabNavigator. By
    default,
    creationPolicy is set to "auto", which means the TabNavigator
    only
    creates the children of the initially visible pane on
    startup--this is
    to make startup faster. In your case, since you need to
    access children
    of the hidden tabs regardless of whether the user visits
    them, you
    should use creationPolicy="all".
    nj
    Flex Builder team

  • CFFORM and tabs

    I have a flash form with multiple tabs. When the user clicks
    the Submit button, I want the form to reload with the same tab on
    top.
    Example: There are two tabs: "Car" and "House". "Car" is the
    top tab. If the user hits submit while on the "House" tab, I want
    the page to reload with the "House" tab selected. Thank
    you!!

    This might not be the best solution, but it works:
    <!--- set default tab to 0 --->
    <cfparam name="thisTab" default="0">
    <!--- selectedindex tells the form which tab to focus on
    --->
    <cfformgroup type="TabNavigator" selectedindex="#thisTab#"
    id="tabs">
    <!--- create a hidden form field and populate it with the
    currently selected tab's index --->
    <cfinput type="hidden" name="thisTab" value="">
    <cfinput type="submit" name="Submit" value="Submit"
    onClick="theForm.thisTab = tabs.selectedIndex;">

  • TabNavigator Child Control Problem on Programmatic SelectedIndex Change

    I've got a TabNavigator that contains another TabNavigator as
    a child control on its second page. On the child TabNavigator
    there's a ViewStack and a couple of Accordion controls. On my first
    parent tab I've got a Button that, when clicked, programmatically
    changes the selectedIndex of the parent TabNavigator to display the
    contents of the second tab (which contains the child TabNavigator).
    I'm finding that when the index of the TabNavigator is
    changed programmatically, all of the controls in the child
    TabNavigator are stacked on top of each other and overlapping as
    though the Flash player has no clue how to display these child
    controls. Once I click through each tab on the child TabNavigator,
    they appear intact. If I click the Button to change the tab again,
    all of the controls will be jumbled and stacked.
    This problem happens 100% of the time. I've changed every
    single control in my app to creationPolicy="all" to no avail.
    Anybody experienced this or know what to do?

    I've got a TabNavigator that contains another TabNavigator as
    a child control on its second page. On the child TabNavigator
    there's a ViewStack and a couple of Accordion controls. On my first
    parent tab I've got a Button that, when clicked, programmatically
    changes the selectedIndex of the parent TabNavigator to display the
    contents of the second tab (which contains the child TabNavigator).
    I'm finding that when the index of the TabNavigator is
    changed programmatically, all of the controls in the child
    TabNavigator are stacked on top of each other and overlapping as
    though the Flash player has no clue how to display these child
    controls. Once I click through each tab on the child TabNavigator,
    they appear intact. If I click the Button to change the tab again,
    all of the controls will be jumbled and stacked.
    This problem happens 100% of the time. I've changed every
    single control in my app to creationPolicy="all" to no avail.
    Anybody experienced this or know what to do?

  • Tabnavigator with swfloader problem

    Hello,
    I'm trying to run a tabnavigator component with each tab having a separate swfloader.  Each swfloader is a different datagrid that I populate with the SystemManager.application['functionName'] = 'parameters' method.
    My problem is that when I a few tabs, only the very last tab's datagrid will have data, and the others will be blank.  What's wrong with it?
                public var matrixLoader:SWFLoader;
                public function addTab(tabName:String, swfURL:String, setFunc:Array, searchString:Array):void {
                    var tabCanvas:Canvas = new Canvas();
                    tabCanvas.label = tabName;
                    tabCanvas.id = tabCanvas.label;
                    tabCanvas.horizontalScrollPolicy = "off";
                    tabCanvas.verticalScrollPolicy = "off";
                    functionName = new Array(setFunc);
                    paramString = new Array(searchString);
                    matrixLoader = new SWFLoader();
                    matrixLoader.minHeight = 100;
                    matrixLoader.minWidth = 100;
                    matrixLoader.percentWidth = 100;
                    matrixLoader.percentHeight = 100;
                    matrixLoader.addEventListener(FlexEvent.UPDATE_COMPLETE, created);
                    matrixLoader.load(swfURL);
                    tabCanvas.addChild(matrixLoader);
                    tabnavi.addChildAt(tabCanvas,tabnavi.numChildren);
                public var loadedSM:SystemManager;
                private function created(event:FlexEvent):void {
                    loadedSM = new SystemManager();
                    if (matrixLoader.content != null) {
                        loadedSM = SystemManager(matrixLoader.content);
                        if (loadedSM.application != null) {
                            for(var i:int = 0; i < functionName.length; i++){
                                loadedSM.application[functionName[i].toString()] = paramString[i].toString();
    Any help would be greatly appreciated.

    Hopefully before you maybe loaded the subapp via
        swfLoader1.source="subapp.swf?foo=1
        swfLoader2.source="subapp.swf?foo=2
    And code somewhere in the Application checked parameters.foo and set foo
    appropriately:
        <mx:Application initialize="checkFoo()"...
        <mx:Script>
            public var foo:int;
            private function checkFoo():void
                foo = parameters.foo;
    Now you just load the module once w/o parameters
        private var modInfo:IModuleInfo = ModuleManager.getModule("module.swf");
    And once the module is ready:
        var module1:IMyModuleInterface = modInfo.factory.create();
        module1.foo = 1;
    And
        var module2:IMyModuleInterface = modInfo.factory.create();
        module2.foo = 2;

  • TabNavigator's tab dynamic visibility handling problem.

    Hello All,
    I am facing problem in TabNavigator component.
    My application has one tabnavigator with 4 tabs. (T1,T2,T3,T4)
    Tabs visibility is depend on data which are load in those tabs.
    If data is getting Null from database for T2, T2 tab will not displayed. Only other 3 are displayed.
    I have tried this....
    myTabNavigator.getTabAt(myTabNavigator.getChildIndex(myT2tab)).visible = false;
    myTabNavigator.getTabAt(myTabNavigator.getChildIndex(myT2tab)).includeInLayout = false;
    but problem is if once tab is hide by above code, will not visible again by setting visibile & includeInLayout property to true.
    Anyone else noticed this, have any suggestions?
    Thank you.

    Hi Tejas S Patel,
    I dont see any such kind of problem...I have run a test...it works perfectly fine.
    Below is the sample test I have done..
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute">
    <mx:TabNavigator width="103" id="tabone">
      <mx:Canvas label="First Canvas" width="100%" height="100%">
       <mx:Label text="First Canvas"/>
      </mx:Canvas>
      <mx:Canvas label="Second Canvas" width="100%" height="100%">
       <mx:Label text="Second Canvas"/>
      </mx:Canvas>
      <mx:Canvas label="Third Canvas" width="100%" height="100%">
       <mx:Label text="Third Canvas"/>
      </mx:Canvas>
    </mx:TabNavigator>
    <mx:HBox top="100">
      <mx:Button id="btn1" label="HIDE SECOND TAB" click="tabone.getTabAt(1).visible=false;tabone.getTabAt(1).includeInLayout=false;"/>
      <mx:Button id="btn2" label="SHOW SECOND TAB" click="tabone.getTabAt(1).visible=true;tabone.getTabAt(1).includeInLayout=true;"/>
    </mx:HBox>
    </mx:Application>
    Thanks,
    Bhasker Chari

  • TabNavigator repeats backgroundImage problem

    I am trying to use a background image in my TabbedNavigator.
    The image appears successfully where it should,
    EXCEPT a small part of it is also repeated behind the tabs.
    I have tried several images of varying sizes, and this occurs every
    time.
    Is this normal behavoir? Is there a way to avoid this? My
    code is:
    <mx:TabNavigator styleName="tabnav"
    backgroundImage="{EmbeddedAssets.BG}" width="805" height="580"
    top="10" left="10">
    where EmbeddedAssets is an AS class containing static
    references to embedded image files.
    Thanks

    quote:
    Originally posted by:
    John Hall
    But if it's always at the same level of a container inside a
    tab, could you refer to the parent and get the selectedIndex before
    you leave and reset it to that selectedIndex
    Tab Navigator has a few events. For mentioned above you have
    to use 2 events:
    1. change - here you have to capture 2 values; oldIndex and
    id. you can't cancel action here because at this moment you don't
    know about validation error.
    2. updateComplete - here you are on new tab and don't have
    info about oldIndex. You have to use captured on first stage info.
    Now you knowabout validator status and can return back to oldIndex.
    There are a lot of additional variables and code involved
    into this process.
    It is really painful to track everything due to TabNavigator
    bug which should fire "Focus out" event for validated object and
    cancel moving to new tab if there was validation error.

  • TabNavigator Problem

    Hi I have quite a complex component within my Flex 2
    application….
    The component consists of numerous tabs within a
    tabNavigator… and each tab contains a dataGrid that displays
    data from a webService relevant to the selected tab.
    This is quite difficult for me to explain in words so I will
    apologise in advance if it makes no sense, but I will give it a
    go…..
    The tabs work fine, and the dataGrids are populated when the
    tabs are changed… when a tab is selected, it passes a
    variable to the web service which then pulls back and displays in
    the dataGrid all relevant data to the sent variable etc….
    Each tab within the tabNavigator contains a different /
    separate dataGrid with a unique name / ID!
    The problem that I am having is when you change the tabs
    quickly, its as if the web service cant keep up and is getting
    confused as to what data to display in what dataGrid
    etc……. although if you move through more slowly it
    works perfectly.
    I thought that maybe a “quick fix” to this is
    maybe to disable elements / tabs within the component until the web
    service has completed loading therefore not allowing the user to
    change tabs (as they are disabled) until the dataGrid has been
    loaded etc….. but I don’t know how to do this :(
    Does anyone know how I can go about doing this, or if there
    is another solution to my problem? - Any suggestions?
    Thanks,
    Jon.

    Hi Biebel37,
    I was able to get a runtime error with a test app I wrote
    doing something similar to what you described. I think what you're
    doing should be legal, so it may be an SDK bug, but I'll file it
    and see if the SDK team agrees :)
    One workaround that might work for you would be to make it so
    that instead of creating the TabNavigator in a given state (using
    AddChild), you put it in the base state, but set visible="false".
    Then, in the state where you want it to appear, use <SetProperty
    target="{nav}" name="visible" value="true"/>. (Depending on how
    you're doing your layout, you may need to set
    includeInLayout="false" in the base state and set it to true in the
    other state as well.) In my test app, this avoids the runtime
    error.
    Thanks,
    nj
    Flex Builder team

  • Tabnavigator problems

    Hi all, I have a Tabnavigator with 5 tabs, each of which has charts of one sort or another. Since migrating to FB4 I get a problem where if the contents of one tab change, suddenly the content of all of them is displayed at the same time which looks absolutely awful. By clicking on each of the tabs the problem is gradually removed. I saw someone else reported this problem on stackoverflow.com:
    http://stackoverflow.com/questions/4638300/tabnavigator-tab-content-retains-strangely-flas hbuilder-4

    Just started getting this problem again with Flash 11.2. I have this in Firefox (debug version) :
    Version: 11.2.202.228
    and this in IE8: (not debug version)
    11.2.202.233
    Has anybody got any ideas on how to resolve it?

  • Problem with tabnavigator index change effect

    Hello All,
         I am using
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application 
    xmlns:mx="http://www.adobe.com/2006/mxml" layout="vertical" verticalAlign="middle" horizontalAlign="center">
    <mx:TabNavigator id="tabNav" height="600" width="600" change="onTabChange(event)">
    <mx:VBox horizontalAlign="center" verticalAlign="middle" height="100%" width="100%" label="Tab 1">
    <mx:Label text="Tab 1" fontSize="30" />
    </mx:VBox>
    <mx:VBox horizontalAlign="center" verticalAlign="middle" height="100%" width="100%" label="Tab 2">
    <mx:Label text="Tab 2" fontSize="30" />
    </mx:VBox>
    <mx:VBox horizontalAlign="center" verticalAlign="middle" height="100%" width="100%" label="Tab 3">
    <mx:Label text="Tab 3" fontSize="30" />
    </mx:VBox>
    <mx:VBox horizontalAlign="center" verticalAlign="middle" height="100%" width="100%" label="Tab 4">
    <mx:Label text="Tab 4" fontSize="30" />
    </mx:VBox>  
    </mx:TabNavigator>
    <mx:Script>
    <![CDATA[
    import mx.effects.Move;
    import mx.events.IndexChangedEvent;
    import mx.events.EffectEvent;
    public function onTabChange(event:IndexChangedEvent):void
    var oldTab:DisplayObject = tabNav.getChildAt(event.oldIndex);
    var newTab:DisplayObject = tabNav.getChildAt(event.newIndex);
    var moveEffect:Move = new Move();
    moveEffect.target = oldTab;
    var moveEffect2:Move = new Move();
    moveEffect2.target = newTab;
    if(event.oldIndex > event.newIndex)
    //Moving old Tab out to the right, new tab in from the left
    oldTab.x = 0;
    moveEffect.xTo = oldTab.width + 100;
    moveEffect.yFrom = oldTab.y;
    moveEffect.yTo = oldTab.y;
    newTab.x = -oldTab.width;
    moveEffect2.xTo = 0;
    moveEffect2.yFrom = oldTab.y;
    moveEffect2.yTo = oldTab.y;
    else
    //Moving old Tab out to the left, new tab in from the right
    oldTab.x = 0;
    moveEffect.xTo = -oldTab.width;
    moveEffect.yFrom = oldTab.y;
    moveEffect.yTo = oldTab.y;
    newTab.x = oldTab.width + 100;
    moveEffect2.xTo = 0;
    moveEffect2.yFrom = oldTab.y;
    moveEffect2.yTo = oldTab.y;
    oldTab.visible = true;
    newTab.visible = true;
    moveEffect2.play();
    moveEffect.addEventListener(EffectEvent.EFFECT_END,tabOffScreen);
    moveEffect.play();
    private function tabOffScreen(event:EffectEvent):void
    event.target.removeEventListener(EffectEvent.EFFECT_END,tabOffScreen);
    event.target.target.visible = false;
    ]]>
    </mx:Script></mx:Application>
    to run the slide effect in flash builder 4.5 with sdk 4.5. When the effect plays, the selected child behaves abnormal whereas when it runs with sdk 3.6 in flash builder 4.5, everything goes well.
    Any help will be apppreciated.
    -Thanks and regards
    Vishal Kumar

    Hi Biebel37,
    I was able to get a runtime error with a test app I wrote
    doing something similar to what you described. I think what you're
    doing should be legal, so it may be an SDK bug, but I'll file it
    and see if the SDK team agrees :)
    One workaround that might work for you would be to make it so
    that instead of creating the TabNavigator in a given state (using
    AddChild), you put it in the base state, but set visible="false".
    Then, in the state where you want it to appear, use <SetProperty
    target="{nav}" name="visible" value="true"/>. (Depending on how
    you're doing your layout, you may need to set
    includeInLayout="false" in the base state and set it to true in the
    other state as well.) In my test app, this avoids the runtime
    error.
    Thanks,
    nj
    Flex Builder team

  • Problem in tabnavigator?

    Hi,
    I have downloaded code for tabnavigator maximize and restore from the net.I have attatched as file.Just download
    and import in ur flex builder.From output u will find tabnavigator maximize,restore and above tabnavigater down arrow
    will be present in top right corner.I have to remove that down arrow,but unable to do that.Here that entire component
    has build based on swc file.How to remove that arrow?Plz help me.I have to use this one in my application  or If u
    have any code for tab navigator maximize or restore plz send me.
    Regards
    D.Mahesh Babu

    Set popUpButtonPolicy to off,
    <code:SuperTabNavigator
              id="mySuperTabNavigator"
              height="50%" width="100%"
              bottom="5" right="5" left="5"
              closePolicy="close_selected"
              popUpButtonPolicy="off"
              tabClose="maxClick(event)">
         <mx:VBox label="Tab 1"/>
         <mx:VBox label="Tab 2"/>
         <mx:VBox label="Tab 3"/>
    </code:SuperTabNavigator>

Maybe you are looking for