Perhaps it is a timing thing
I think so too - I had so far only tested with my work .ini and with my Extended menu which adds a second user defined .ini of about 500 em_commands.
If I turn off my Extended menu (using the build in English language file), I can reproduce the bug as you describe in 64bit TC in
both Normal and Dark mode under Windows 10, but
only in Normal mode under Windows 7
Under Windows 10 in 32bit TC, If I enable my Extended menu - so that the Command browser has to read the additional .ini file - then the buttons are always already missing after the first click on All in both Normal and Dark mode. Without the Extended menu .ini, the buttons are always shown both after the first and the second click on All.
Under Windows 7 in 32bit TC I can reproduce the bug as described, but
only in Dark mode - in Normal mode the buttons are already missing at the first click on All.
So there seems to be at least four conditions determining this behavior:
- The presence of a (large) alternative .ini file with user commands (loaded if it has the same name as the currently used .mnu file)
- The bitness of TC
- The Windows version
- The use of Normal or Dark mode