OPENBAR doesn't set ButtonBar=1 in [Layout]

[MVV]

Is it error or by design? When I switch buttonbar using cm_VisButtonbar, TC sets ButtonBar parameter immediately. But if buttonbar is disabled, ButtonBar parameter still keeps value 0 after calling OPENBAR.

[petermad]

OPENBAR is only for loading a .bar file temporarily - Next time you start TC, the buttonbar that is selected as default ([Buttonbar] Buttonbar=path) is still selected (not the bar you opened with the BUTTONBAR command), and if displaying the buttonbar wasn't chosen in Layout, it is still not chosen.

[MVV]

I think it may confuse user (as it has confused me and some other people from Russian board) - if he sees buttonbar, he thinks that it is enabled (and checkbox in configuration dialog says that it is enabled), but really it is disabled...

It would be useful to have some parameter for this command (or maybe a key in wincmd.ini) to change this behaviour to expected one.

[ghisler(Author)]

OPENBAR is indeed meant to switch between multiple button bars, not to set a new default button bar. It's like when you have a button with a .bar file as the command: It also just switches the bar without setting a new default.

[MVV]

Christian, I understand that OPENBAR doesn't set new bar as default bar. But it is strange that it doesn't set 'button bar enabled' parameter to 'true' when enables buttonbar. It causes TC to start with disabled buttonbar in cases when it was enabled on last TC close (if it was enabled via OPENBAR).

[ghisler(Author)]

The idea is that people who normally don't use a button bar can still use one temporarily.

[MVV]

Ok, I've got the reason. But maybe you can add some command that will work in other way?