-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Mouse pointer "vanishes" when moved over Terminal Window #18335
Comments
@inoperable Could you add any more details/? That PR merged literally 5 days ago, I'm not sure it's even in a canary build currently |
At some point the mouse pointer vanishes permanently after alt tab, I'm not sure what triggers it though. When restarting the terminal it seems fine for a while and then it start again. It's weird, I thought it's because software rendering first, but nope,also toggled some other settings but I can't figure out when exactly it decides I don't need a mouse pointer shown at all. Will update if I can pinpoint it more Drives me nuts |
It trigger must be in some onmouseover event handling on terminal window, not over the tab strip or borders (if that's of sny help). I'll get back to once I got more |
Oh, and please confirm with us what exact version(-number) of Windows Terminal you're using. 🙂 |
It's not the behavior intended, I'm very sure about it, the is setting OS mouse settings is a good point to eliminate culprits - but it's not it. Term is 1.23.241213001-llm, OS 27764.1000 & 19045.4651 |
And this seems to be only a 27xxx insiders build exklusive, since I can't replicate it with 19045.xxxx o.O - so I guess I just wasted your time unnecessary... |
It's definitely a insiders build exclusive, I couldn't replicate the same on 19045.4651. I apologize for confusions therefore, maybe this is not entirely a waste of time since this might make a come back agai, I'll fiddle around with the insiders build again and will update this thread once I know more when/how |
It's possible that this is a bug across any Windows 11 version, because I did struggle quite a bit with making cursor hiding work right. The problem is that the WinUI APIs for doing so are just kind of bad and not very robust. It would not surprise me if they broke between Windows versions. |
Leading theory: The current cursor that we get from the WinUI API is non-null but also hidden. This means that when we restore it, we restore a hidden cursor that won't ever go away, because nothing explicitly sets a visible cursor in our code either. Ideally, WinUI would have a cursor stack that you can push/pop into, but in the absence of that we'll just do the next best thing:
|
So, to clarify @lhecker I think you are right, and have it figured out (as mentioned above) |
Originally posted by @zadjii-msft in #18215 (comment)
Probably this
The text was updated successfully, but these errors were encountered: