mirror of
https://github.com/keycastr/keycastr.git
synced 2026-05-15 14:15:50 -06:00
[GH-ISSUE #19] it seems that the key display out the screen on OSX 10.10.1 #16
Labels
No labels
bug
compatibility
discussion
documentation
enhancement
help wanted
help wanted
investigation needed
pull-request
release
visualizer
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/keycastr#16
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @taizilongxu on GitHub (Dec 22, 2014).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/19
I type the delete and then
@graphicbeacon commented on GitHub (Dec 27, 2014):
I am also experiencing the same issue. I have an external monitor attached to my macbook pro–don't know if the positioning of the key logs are affected by that.
@petrowsky commented on GitHub (Jan 22, 2015):
I just tried this out on 10.10.1 and all settings in privacy are good. Application is within /Applications. I get nothing on screen. Activity monitor does show the app is running. Just nothing on screen.
Here's a screenshot of the plist. Looking in the code for NSWindow calls I see 10 10 200 100. I'm guessing this is the initial when no prefs file exists? For some reason mine keeps showing the values in the image. Does this type of info help?
@mgarciaisaia commented on GitHub (Feb 13, 2015):
I'm experiencing this same problem but on OSX 10.9.5
May it be retina-related?
If I change the resolution (in Displays) and then re-launch KeyCastr, it appears on different parts of the screen.
@ashfinal commented on GitHub (Feb 15, 2015):
Just install KeyCastr and really happy now. : ) and I'm on 10.10.2.
Yes, the initial position is out of screen a bit, but the point is you can drag the window to anywhere you want! Here is my experience that you can do to solve this problem:
Hold any key for a long time, you should see the windows with your typing now. Before it fades out, you can drag the window to where you want it to be.
And now you are happy to go! Problem solved!
@akitchen commented on GitHub (Mar 16, 2015):
Hey @petrowsky Yes this info helps
@mgarciaisaia I don't think it is retina related.
My experience is mostly the same as @ashfinal , but I think we should look into possible fixes for detecting a corrupted stored NSFrame, and refactor related code to be more reliable on modern OS X versions
@Grae-Drake commented on GitHub (Jun 23, 2015):
Hey @akitchen, had the same problem here. Happy to help troubleshoot if I can.
@akitchen commented on GitHub (Jun 23, 2015):
There are a few issues in the code conspiring to cause this, which the changes in
ddf8ed8f77cause to manifest when installed on new machines.I completely agree, this needs to be fixed. It's top-of-list for the next time I have time to dig into it.
For now, turn off "Display only command keys" and hold down a key. Eventually the visualizer will appear and you can drag it.
@akitchen commented on GitHub (Jul 12, 2015):
There are commits on master which fix this issue; will publish a new version
@akitchen commented on GitHub (Jul 12, 2015):
Please try out v0.8.5 and let us know if the problem remains
@taizilongxu commented on GitHub (Jul 14, 2015):
Nice, I have update the v0.8.5 and it works well in OSX 10.10.4
@akitchen commented on GitHub (Sep 26, 2015):
Thanks for confirming @taizilongxu !