Folder tabs don't display

[mariola]

Folder tabs don't display after restarting the FC when tab position is "Bottom"
FreeCommander XE 2014 Build 650, Windows 7 SP1 32-bit

[joby_toss]

I can't replicate this issue on my win7x64.
Did you uncheck "Close all not locked tabs when the program ends" option?

[Dreamer]

Can't confirm it either. Win Vista 32 bit.

[mariola]

I have tried to uncheck the "Close all not locked tabs..." option, but it is still the same...

I have one tab opened in both panes.
When the tab position is "Bottom" and I close the app and then run it again, it opens without tabs (see below).
When the tab position is "Top", everything works fine...

[joby_toss]

Could you change you settings like this and retry, please?

[mariola]

I have found it! It is caused by the "Cut corner" tab style.
When I use different tab style, it is ok - pls test it...
Thanks.

[joby_toss]

Yes, you are right, that's a bug! Nice job finding it!

[Dreamer]

Confirmed, it's a strange bug.

BTW all options except "round corners" and "square corners" are broken, not just the "cut corner" option.

[joby_toss]

Still not fixed in beta 654.

P.S. not being impatient, just bumping this one...

[Dr_Eyeball]

Wow, I just had this bug again in FreeCommander XE 2025 Build 920 64-bit donor

I don't know what triggered it. I really struggled to restore the visibility of the folder tabs until I found this post.

I tried:

• restarting, dual/single, horizontal/vertical panes, tree list on/off, favourites on/off, image preview on/off, etc.
• most of the checkbox Settings under the Folder Tabs -> Tab Management (tab), plus the Tab General (tab).
• I was tempted to try one of the restore/default settings options under Tools menu, but wasn't sure what they might do.

Solution:
Although it did not fix it the first time I tried it, it still seems to be caused by one of the "Cut corner" tab styles, as previously stated.
When I used Round or Square corners, it eventually fixed it.

It is good to keep these old solutions. Thanks.

[Marek]

Thanks for reporting it.
Found and fixed for the next release.