Console::setActive(true) doesn't work as expected

[Amerio.Stephane]

Hello,

Tried this code to circumvent current limitation with keyboard handling in console management, but as explained in the code comments, it doesn't work as expected.

// Doesn't work. The console can be hidden, but never shown
if (App::clearKeyState(App::KEY_F1)) {
	Console::setActive(!Console::isActive());
}
// Doesn't work. The console cannot be opened with this.
// If the console is already open, then it will quick-close-open it again. (???)
if (App::clearKeyState(App::KEY_F2)) {
	Console::setActive(true);
}
// Works OK. Closes the console
if (App::clearKeyState(App::KEY_F3)) {
	Console::setActive(false);
}
// isActive Works ok, but strangely clearKeyState doesn't as it clearly auto-repeat keys
// based on OS setup. Shouldn't the key NOT auto-repeat? Or is there another fct for this behavior? 
if (App::clearKeyState(App::KEY_F4)) {
	Log::message("active=%d\n",Console::isActive());
}

Also, Console::run("show"); doesn't work either.

Can you advise?

Edited February 26, 2021 by Amerio.Stephane

[silent]

Hi Stephane,

Could you please elaborate what kind of task you are trying to achieve?

Thanks!

[Amerio.Stephane]

Just showing/hiding the console through code

[silent]

Yeah, there is a small bug in the setActive() method. We've already fixed it in our internal builds.

Bug fix will be available in the upcoming 2.14 SDK update.

[artem.suravikin]

Hello,

Is there any workaround to fix it in the version 2.13?

[silent]

Hi Artem,

I'm afraid there is no workaround available for this behavior since the bugged logic is deeply inside the engine sources (and there is no other methods with similar behavior that can be used instead).

Thanks!