[BUG] Command line access with RestrictInterface=2

[bugmenot]

Reproduce:
Restrict command line access in wincmd.ini:
RestrictInterface=2

Restart TC
Note command line is not visible/accessible.
Press keyboard shortcut ALT-F8 (command line history)

Expected: Nothing happens.
Actual: Command line history is displayed and command line access.

[Flint]

Confirm!

[ghisler(Author)]

I will check that, thanks.

[ghisler(Author)]

This should be fixed, please confirm!

[Flint]

Fixed, but not completely!
1. Press Ctrl+E: the cursor moves to the hidden command line and becomes invisible. If you have a menu item or a button on the buttonbar with the command cm_FocusCmdLine, it becomes "selected".
2. Type e.g. cmd (you have to do it blindly, but the autocomplete drop-down list is shown!), press Enter.
3. cmd.exe is started.

Of course, if you call cm_NextCommand or cm_PrevCommand from the menu the result is the same as above: you access the command line, though invisibly.

With Ctrl+P, Ctrl+Enter, Ctrl+Shift+Enter and Alt+F8 I could not access the command line, as well as with the direct call of cm_FocusCmdLine.

[ghisler(Author)]

Press Ctrl+E

Please report new bugs in a new thread.

[Flint]

Please report new bugs in a new thread.

Hmm... I would not treat it as a new bug. The topic title says:
Command line access with RestrictInterface=2
I just reported that this bug has not been fixed completely, there is still a way to access the command line with RestrictInterface=2 (the only difference is the hotkey used).

But OK, if this is more convenient to you, I created a new thread for this problem.

[ghisler(Author)]

Thanks for starting a new thread!