Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Weird input focus behavior on v1.2.0 #96

Closed
fmiqbal opened this issue Jun 27, 2021 · 4 comments
Closed

Weird input focus behavior on v1.2.0 #96

fmiqbal opened this issue Jun 27, 2021 · 4 comments

Comments

@fmiqbal
Copy link

fmiqbal commented Jun 27, 2021

Recently I upgrade to v1.2.0 from v1.1.1 but I found weird behavior that I can confirm not from windows terminal, already try windows terminal 1.7, 1.8, 1.9-preview, but no avail. I use full screen, always on top, hide on lost focus

The problem is when I focus other window and the quake hide, when I toggle open again, the cursor become on top rather than showing previous scroll, expected like this:

image
image

But instead got this

image
image

The cursor always on top and hide everything before it, I need to scroll to see previous command and result. This also happen when I start to type, the window instantly focus to current input, and make the input on top, again, hiding everything before it.

v1.1.1 doesn't have this issue

Quake config, but I recently learned that using vanilla config also have this issue:

{
	"HotKeys": [
		{
			"Modifiers": "Alt",
			"Key": "Escape"
		}
	],
	"Notifications": true,
	"Opacity": 90,
	"ToggleDurationMs": 15,
	"ToggleAnimationFrameTimeMs": 15,
	"VerticalOffset": 0,
	"VerticalScreenCoverage": 100,
	"HorizontalAlign": "Center",
	"HorizontalScreenCoverage": 100,
	"HideOnFocusLost": true,
	"AlwaysOnTop": true,
	"StartHidden": false,
	"PreferMonitor": "WithCursor",
	"MonitorIndex": 1,
	"Logging": true
}

Windows 10 Version Dev (OS Build 21390.2025)

@fmiqbal
Copy link
Author

fmiqbal commented Jun 27, 2021

weird

@flyingpie
Copy link
Owner

@fmiqbal Thank you for reporting this issue! I think this might be due to the recently added different toggle mode, could you try to add the following and see if it changes anything?

{
	"ToggleMode": "Move"
}

@fmiqbal
Copy link
Author

fmiqbal commented Jun 28, 2021

Nice, thank you, that's fixed it

@fmiqbal fmiqbal closed this as completed Jun 28, 2021
@flyingpie
Copy link
Owner

The default toggle mode has been changed to "Move", on version 1.3.0, to prevent this issue, seeing that there are perhaps more cases of this then vertical monitor setups, which was the reason for the "Resize" mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants