In tests, a fresh install, both tabs are easy to see/distinguish and the active one appears slightly bold in font.
With the same version on two other machines 7 & 10, the inactive tab text is barely visible. Taking my INI from my other machines also causes the problem on the fresh install.
Same INI causes the problem in v19 too.
Any idea what setting would affect tab appearance?
I tried every theme. Only "Office 2007 Black" and "Office 2010 Black" had that text in white.
In addition, merely switching themes may not show the correct color text on inactive toolbar tabs. If that color is going to switch between black and white, it does so only after TCMD has been restarted.
Yes, both myself and Vince saw the illustrated behavior using both Office Black themes as mentioned above. When changing themes you have to restart TC for some of the changes to take effect. Even after restarting though, I see the white text shown above. Seeing it on Win7 & 10.
It's not critical, but I was hoping it would be an easy thing to fix.
I realize Windows actually draws the controls but TCMD or some 3rd party control you use instigates the control, right?
Reproducible in a clean Win7x64 VM. The issue arrived with v17. Looks like you unticked the "Luna colors" option and changed the "Appearance set" from VS 2003 to something else. So that explains the change in tab appearance. Given you're using the latest libraries though, seems like a bug in the libraries. Their tabbed toolbar samples don't offer a 'black' theme so I can't fully test the current libraries without getting an eval and building it.
Same problem here on Win 10 Pro x64 (Clean Install) (with v19.00.39) and Office 2007 black theme ...
EDIT: Problem is with ALL themes (more or less). Even with some others inactive tabs are almost invisible!
The worst is Office 2013 - there inactive tabs are completely invisible.
@Rex: you say, not TCMD is responsible. Okay. Just: this tab function is so practically unusable (at least with some themes) ...
- "Office 2007 Schwarz (black)":
- "Windows 7":
- "Office 2013":
And note: I have NOTHING changed related to such a behaviour after my clean Win 10 installation. So HOW could *I* resolve this? All are default values for Win themes etc.
@Alpengreis, I suspect you'll find that the Office Black themes are the only ones with the problem. In your Office 2013 example above, if you exit then restart TCMD, you should be able to see the tabs. That's an undocumented quirk in the dynamic switching of themes. Glad to see I'm not the only one seeing this behavior!
As for the responsibility comment by Rex, as a developer I understand his viewpoint. Technically TCMD is indirectly responsible because it's using a 3rd party library to implement some of the TCMD GUI. There are times when updates to these libraries can introduce problems that the library developer and end user could not anticipate or control.
In this case, it seems Rex tweaked the parameters in v17 used to define the tabs in a way that revealed this issue. Aside from undoing that change, his only option may be to wait on the developer of the library he uses to fix their code. Others using this same library are also reporting similar behavioral issues.
Indeed, after restart I see the tabs (tested with "Windows 7"). I saw something in other thread about restart after change the theme and even about a library problem - just forgot yesterday ...)! My fault!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.