Total Commander

Currently when a .bar file is used as the command in a button, then that button is not shown when the button bar is opened as a menu. That is convenient when you want a "Go back to parent bar" button, that is it not shown when the button bar is opened as a menu.

I would be nice if the commands OPENBAR, OPENBAR1, OPENBAR2, OPENBAR *, OPENBAR1 * and OPENBAR2 * could be treated the same way as when there is just a .bar file in the command line

Are you sure about that? The user may want to e.g. replace the vertical bar through a button bar menu command, e.g. when he has 100s of bars...

Then maybe just enable it for OPENBAR *, OPENBAR1 * and OPENBAR2 * - which will usually be used to go back to the default bar from a subbar.

Why not just use the bar name to go back? This has the advantage that it works even when the bar file is used for the vertical bar. The OPENBAR commands are meant to open a bar either from somewhere else, like the command line or a hotkey, or to change the OTHER bar (e.g. vertical bar from main bar).

Why not just use the bar name to go back?

I provide several button bars with my Extended Menus and with my TC Languagebar. I have no way of knowing the name of the Users default bar, to use in the provided "Return to default bar" button in those bars - that is why OPENBAR * is a good improvement - before that I used a button with the command: - to go back to the default bar, but this kind of button is also not hidden in Menu mode.

Also if I change the default bar file, I would have to update all "Return to default bar" buttons - not very convenient.

Since OPENBAR * is a new feature - this is the time to decide that buttons with this command are invisible in Menu mode.

maybe adding a parameter to OPENBAR like /H (which would hide the button if opened as a menu) could solve that?