Odd behavior when closing tabs

[AimHere]

Hi,

I use the tabbed browsing feature of FCXE a lot. I've noticed a problem with the way the program behaves when closing tabs.

If I have multiple tabs open, and close any but the leftmost one, the program switches focus to the next one to the left, displaying the associated folder's contents in the file pane, as expected.

But if I close the leftmost tab, the program switches focus (on the tab bar) to the next tab to the right... but continues to show the contents of the just-closed tab in the file panel.

If I then refresh (Ctrl-R), it continues showing the incorrect folder contents, and often will change the tab's label to match the incorrect folder, "forgetting" the label and folder that had been previously displayed on that tab.

The only way I can get the active tab to show the correct contents after closing the leftmost tab is to immediately switch to another tab (assuming I have any open), then back to the previously-focused one.

Here's an example: Suppose I have three tabs open, displaying the contents of folders "A", "B", and "C", in that order. I then close tab "C", leaving me with "A" and "B". Tab "B" (which was to the left of "C") becomes the active/focused one, and the file pane displays the contents of folder "B", as expected.

Now, suppose I again have tabs "A", "B", and "C". I click on tab "A" and close that one, leaving tabs "B" and "C". Tab "B" gains focus (becomes the active tab)... but the files pane continues to show the contents of folder "A", not folder "B"! If I refresh at this point, the label of the now-active tab "B" changes to "A", and the files pane continues to show the contents of "A". (If, instead of refreshing, I click on tab "C", then back on tab "B", the files pane then displays folder "B"'s contents again.)

This doesn't make any sense. The files pane needs to always show the contents of the active tab, but right now it behaves differently when closing the leftmost tab than it does when closing any other tab. Please fix.

[joby_toss]

Confirmed.

[AimHere]

One of the more recent FCXE updates seems to have fixed this. Thanks.