bConsumeAltSpace

Development Pipeline & Plugins
, ,
1

Hi!

We use Alt+Shift+{Key} keybinds for our debug setup; totally normally. But we ran into a funky issue where alt space was getting eaten up by the Windows Context Menu, but this was only happening in Editor/PIE! We dug in, and found some interesting code that causes the divergence between editor and packaged game.

in WindowsApplication.cpp

	if (!GIsEditor)
	{
		GConfig->GetBool(TEXT("WindowsApplication"), TEXT("bConsumeAltSpace"), bConsumeAltSpace, GEngineIni);
	}

my question… is there any harm from letting this config variable work in editor and packaged builds? bConsumeAltSpace actually already defaults to false, so the behavior wouldn’t change for everybody. But it’d be nice for games to be able to customize whether or not they use alt+space+{other optional modifiers} for things

Personally, I’d just kill the !GIsEditor check and call it a day

2

Steps to Reproduce

3

Hi there,

As you’ve identified, the only ramification here would be that this input doesn’t get passed through to open the window system menu. If you’re fine with this being the case in the editor, then you can safely remove the check to set that boolean.

The default behaviour just aligns the editor to how most, but not all, other windows desktop applications handle this input.

Thanks,

Hayden