Shortcut to "Toggle Maximize Area" is listed in the menu but does not work as labeled. #67203

New Issue

hudson barkley · 2019-07-19T02:55:22+02:00

hudson barkley commented

2019-07-19 02:55:22 +02:00

Blender Version
Broken: 2.80

Short description of error
Now that the ctrl-up shortcut to maximize the area is gone, this brings up the issue that the ctrl-space is already used in the console for auto-complete, and thus there is no longer a shortcut to maximize the console area.

**Blender Version** Broken: 2.80 **Short description of error** Now that the ctrl-up shortcut to maximize the area is gone, this brings up the issue that the ctrl-space is already used in the console for auto-complete, and thus there is no longer a shortcut to maximize the console area.

hudson barkley commented

2019-07-19 02:55:22 +02:00

Added subscriber: @snuq

blender-admin commented

2019-07-19 02:55:22 +02:00

#68556 was marked as duplicate of this issue

Gavin Scott commented

2019-07-19 04:24:18 +02:00

Added subscriber: @GavinScott

Gavin Scott commented

2019-07-19 04:24:18 +02:00

Have you tried CTRL-ALT-SPACE?

Both CTRL-SPACE and CTRL-ALT-SPACE are defined in the default keymap for this function. CTRL-ALT-SPACE seems to work everywhere for me.

Have you tried CTRL-ALT-SPACE? Both CTRL-SPACE and CTRL-ALT-SPACE are defined in the default keymap for this function. CTRL-ALT-SPACE seems to work everywhere for me.

hudson barkley commented

2019-07-19 06:30:42 +02:00

Ah yeah, ctrl-alt-space works. I guess the menu in the console area should be changed to reflect this? right now it lists ctrl-space as the shortcut.

Gavin Scott commented

2019-07-19 07:07:56 +02:00

Yes, that's a valid point. Below is what the header context menu looks like for reference. Not sure if it could easily be smart enough to show the ALT version only if there's an overriding conflicting keymap. So I think this really isn't a bug so much as an enhancement request to make the automatic keybind display smarter. I'll leave it for someone else to decide if it's worthy of keeping as a bug.

(If the menu display bothers you, you can go into the keymap and use the search function to look for functions with toggle in the name, and that will put the two key bindings under Screen at the top. Open them both up and toggle the ALT selector button in each one which will make the CTRL-ALT-SPACE version listed first, and then it will start showing up as the shortcut (in ALL your headers).

Yes, that's a valid point. Below is what the header context menu looks like for reference. Not sure if it could easily be smart enough to show the ALT version only if there's an overriding conflicting keymap. So I think this really isn't a bug so much as an enhancement request to make the automatic keybind display smarter. I'll leave it for someone else to decide if it's worthy of keeping as a bug. (If the menu display bothers you, you can go into the keymap and use the search function to look for functions with toggle in the name, and that will put the two key bindings under Screen at the top. Open them both up and toggle the ALT selector button in each one which will make the CTRL-ALT-SPACE version listed first, and then it will start showing up as the shortcut (in ALL your headers). ![image.png](https://archive.blender.org/developer/F7617747/image.png)

Campbell Barton changed title from ~~Shortcut to "Toggle Maximize Area" in console is broken~~ to Shortcut to "Toggle Maximize Area" is listed in the menu but does not work as labeled.

2019-07-19 09:26:39 +02:00

Campbell Barton commented

2019-07-19 09:40:08 +02:00

Added subscriber: @ideasman42