[GH-ISSUE #25] Can't get it to work #24

Closed
opened 2026-05-05 04:44:23 -06:00 by gitea-mirror · 16 comments
Owner

Originally created by @felippenardi on GitHub (May 8, 2015).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/25

It was working fine, but suddenly it stopped.

I've already tried to reinstall, check permissions on "Security & Privacy", but it will never display the keys. Can someone help me troubleshoot it?

Originally created by @felippenardi on GitHub (May 8, 2015). Original GitHub issue: https://github.com/keycastr/keycastr/issues/25 It was working fine, but suddenly it stopped. I've already tried to reinstall, check permissions on "Security & Privacy", but it will never display the keys. Can someone help me troubleshoot it?
Author
Owner

@akitchen commented on GitHub (May 8, 2015):

Have you tried removing it from security and privacy, and re-adding it? Sometimes this is necessary in more recent versions of OS X when keycastr's settings have changed.

On Fri, May 8, 2015 at 12:54 PM, Felippe Nardi notifications@github.com
wrote:

It was working fine, but suddenly it stopped.

I've already tried to reinstall, check permissions on "Security & Privacy", but it will never display the keys. Can someone help me troubleshoot it?

Reply to this email directly or view it on GitHub:
https://github.com/keycastr/keycastr/issues/25

<!-- gh-comment-id:100341194 --> @akitchen commented on GitHub (May 8, 2015): Have you tried removing it from security and privacy, and re-adding it? Sometimes this is necessary in more recent versions of OS X when keycastr's settings have changed. On Fri, May 8, 2015 at 12:54 PM, Felippe Nardi notifications@github.com wrote: > It was working fine, but suddenly it stopped. > > ## I've already tried to reinstall, check permissions on "Security & Privacy", but it will never display the keys. Can someone help me troubleshoot it? > > Reply to this email directly or view it on GitHub: > https://github.com/keycastr/keycastr/issues/25
Author
Owner

@felippenardi commented on GitHub (May 8, 2015):

I used to do it every time I used Keycastr—on Yosamite. But it won't do now.

<!-- gh-comment-id:100352542 --> @felippenardi commented on GitHub (May 8, 2015): I used to do it every time I used Keycastr—on Yosamite. But it won't do now.
Author
Owner

@akitchen commented on GitHub (May 8, 2015):

Does the svelte visualizer work for you? Or does the app exit on startup with a 'catastrophic error' dialog displayed?

On Fri, May 8, 2015 at 1:26 PM, Felippe Nardi notifications@github.com
wrote:

I used to do it every time I used Keycastr—on Yosamite. But it won't do now.

Reply to this email directly or view it on GitHub:
https://github.com/keycastr/keycastr/issues/25#issuecomment-100352542

<!-- gh-comment-id:100353127 --> @akitchen commented on GitHub (May 8, 2015): Does the svelte visualizer work for you? Or does the app exit on startup with a 'catastrophic error' dialog displayed? On Fri, May 8, 2015 at 1:26 PM, Felippe Nardi notifications@github.com wrote: > ## I used to do it every time I used Keycastr—on Yosamite. But it won't do now. > > Reply to this email directly or view it on GitHub: > https://github.com/keycastr/keycastr/issues/25#issuecomment-100352542
Author
Owner

@felippenardi commented on GitHub (May 8, 2015):

Good guess! It doesn't exit on startup anymore since the last time I re-authorized on Security panel, but the svelte indeed works!

The thing is: the only keys svelte will highlight are the ones in the bottom (shift, control, option and command). It doesn't catch "cmd+tab" or "option+n" and so on. Any guess?

<!-- gh-comment-id:100355366 --> @felippenardi commented on GitHub (May 8, 2015): Good guess! It doesn't exit on startup anymore since the last time I re-authorized on Security panel, but the svelte indeed works! The thing is: the only keys svelte will highlight are the ones in the bottom (shift, control, option and command). It doesn't catch "cmd+tab" or "option+n" and so on. Any guess?
Author
Owner

@motiko commented on GitHub (May 13, 2015):

Same issue here, on Yosemite.

<!-- gh-comment-id:101825019 --> @motiko commented on GitHub (May 13, 2015): Same issue here, on Yosemite.
Author
Owner

@motiko commented on GitHub (May 13, 2015):

I was able to fix it by enlarging the font to maximum and dragging the window into the visible area.
Svelte mode still shows only command buttons (shift alt cmd) .

<!-- gh-comment-id:101828472 --> @motiko commented on GitHub (May 13, 2015): I was able to fix it by enlarging the font to maximum and dragging the window into the visible area. Svelte mode still shows only command buttons (shift alt cmd) .
Author
Owner

@felippenardi commented on GitHub (May 14, 2015):

Couldnt replicate that. How can I totally uninstall it? It keeps remembering my settings

<!-- gh-comment-id:102066271 --> @felippenardi commented on GitHub (May 14, 2015): Couldnt replicate that. How can I totally uninstall it? It keeps remembering my settings
Author
Owner

@akitchen commented on GitHub (May 14, 2015):

Where was this build downloaded from?

On May 14, 2015, at 8:08 AM, Felippe Nardi notifications@github.com wrote:

Couldnt replicate that. How can I totally uninstall it? It keeps remembering my settings


Reply to this email directly or view it on GitHub.

<!-- gh-comment-id:102088864 --> @akitchen commented on GitHub (May 14, 2015): Where was this build downloaded from? > On May 14, 2015, at 8:08 AM, Felippe Nardi notifications@github.com wrote: > > Couldnt replicate that. How can I totally uninstall it? It keeps remembering my settings > > — > Reply to this email directly or view it on GitHub.
Author
Owner

@felippenardi commented on GitHub (May 14, 2015):

Last one was the one in github. But something strange just happened: I closed my mac and when I opened it again, Keycastr started working. It is working perfectly. Can't understand what happened.

I did enlarged the fonts, so when it started working I saw large fonts on my screen. But I did tried before with no success.

Thank you everyone for helping troubleshooting it.

Should we left this issue open so someone can find and fix the root of the problem?

<!-- gh-comment-id:102094258 --> @felippenardi commented on GitHub (May 14, 2015): Last one was the one in github. But something strange just happened: I closed my mac and when I opened it again, Keycastr started working. It is working perfectly. Can't understand what happened. I did enlarged the fonts, so when it started working I saw large fonts on my screen. But I did tried before with no success. Thank you everyone for helping troubleshooting it. Should we left this issue open so someone can find and fix the root of the problem?
Author
Owner

@akitchen commented on GitHub (May 16, 2015):

I have only seen issues like this when using the build available for download on popular internet download sites.

we need to cut a new version and publish it, but unfortunately it is blocked on being able to reflect the version number in the about screen. Currently that nib is in an unreadable format, making it hard/impossible to edit. If anybody has any ideas or knows how to convert it, a contribution would be most welcome.

<!-- gh-comment-id:102664313 --> @akitchen commented on GitHub (May 16, 2015): I have only seen issues like this when using the build available for download on popular internet download sites. we need to cut a new version and publish it, but unfortunately it is blocked on being able to reflect the version number in the about screen. Currently that nib is in an unreadable format, making it hard/impossible to edit. If anybody has any ideas or knows how to convert it, a contribution would be most welcome.
Author
Owner

@akitchen commented on GitHub (Jun 7, 2015):

@felippenardi I ran into this again recently, and tracked it down that the OS wasn't sending keyDown events in some cases, even though it sent modifier events for just the cmd/option/ctrl keys. At the time I had Xcode open, and upon closing Xcode it started working again. Not sure if that's related.

Anyway, this doesn't seem to be a bug in KeyCastr, so I'm closing this. Please try the new version out and let us know if you run into other problems. Thanks!

<!-- gh-comment-id:109679969 --> @akitchen commented on GitHub (Jun 7, 2015): @felippenardi I ran into this again recently, and tracked it down that the OS wasn't sending keyDown events in some cases, even though it sent modifier events for just the cmd/option/ctrl keys. At the time I had Xcode open, and upon closing Xcode it started working again. Not sure if that's related. Anyway, this doesn't seem to be a bug in KeyCastr, so I'm closing this. Please try the new version out and let us know if you run into other problems. Thanks!
Author
Owner

@felippenardi commented on GitHub (Jun 7, 2015):

It is still not working... @akitchen How can I delete the settings and anything more Keycastr may store on my computer?

When I delete and open it again, the settings remains persistent.

<!-- gh-comment-id:109790145 --> @felippenardi commented on GitHub (Jun 7, 2015): It is still not working... @akitchen How can I delete the settings and anything more Keycastr may store on my computer? When I delete and open it again, the settings remains persistent.
Author
Owner

@akitchen commented on GitHub (Jun 8, 2015):

I would like to separate this into two new issues, as there are two slightly different symptoms I think we understand. Then we can figure out how to fix them.

  1. user doesn't see one of the visualizers because of a crazy frame stored in NSUserDefaults; the other visualizer works fine.
  • this could maybe happen if the user moved the visualizer around once when on a larger-than-normal display, like a fancy TV or mac with an usual custom screen scale. Try scaling the display and/or increasing the font size to find your visualizer.
  1. user doesn't see the default visualizer at all, and the Svelte visualizer only shows modifier keys.
  • The app has stopped receiving keyDown events from the OS, but still receives events when modifier keys change.
  • This is strange because the same event tap registers callbacks for both events, yet one stops firing. Might be a quirk specific to certain versions of OS X (i.e., a bug)

@felippenardi if your svelte visualizer is displaying all keystroke info correctly, then your are in case # 1 above. Try changing your display scale to find your default visualizer. Also try adjusting the font all the way up in KeyCastr preferences. I think we should work on providing a reset mechanism for users in this case.

If your svelte visualizer is only displaying modifier keys, then you are in case # 2 outlined above. Try closing developer tools or restarting OS X. This one actually doesn't seem to be a KeyCastr bug, believe it or not.

<!-- gh-comment-id:109853552 --> @akitchen commented on GitHub (Jun 8, 2015): I would like to separate this into two new issues, as there are two slightly different symptoms I think we understand. Then we can figure out how to fix them. 1) user doesn't see one of the visualizers because of a crazy frame stored in NSUserDefaults; the other visualizer works fine. - this could maybe happen if the user moved the visualizer around once when on a larger-than-normal display, like a fancy TV or mac with an usual custom screen scale. Try scaling the display and/or increasing the font size to find your visualizer. 2) user doesn't see the default visualizer at all, and the Svelte visualizer only shows modifier keys. - The app has stopped receiving keyDown events from the OS, but still receives events when modifier keys change. - This is strange because the same event tap registers callbacks for both events, yet one stops firing. Might be a quirk specific to certain versions of OS X (i.e., a bug) @felippenardi if your svelte visualizer is displaying all keystroke info correctly, then your are in case # 1 above. Try changing your display scale to find your default visualizer. Also try adjusting the font all the way up in KeyCastr preferences. I think we should work on providing a reset mechanism for users in this case. If your svelte visualizer is only displaying modifier keys, then you are in case # 2 outlined above. Try closing developer tools or restarting OS X. This one actually doesn't seem to be a KeyCastr bug, believe it or not.
Author
Owner

@liuxueyang commented on GitHub (Sep 6, 2016):

Well, it does not work on OS X 10.11.6 as well... even I set the font size to max.

<!-- gh-comment-id:244832174 --> @liuxueyang commented on GitHub (Sep 6, 2016): Well, it does not work on OS X 10.11.6 as well... even I set the font size to max.
Author
Owner

@akitchen commented on GitHub (Sep 6, 2016):

It works fine for me on that same version of OS X. This probably has more
to do with your settings somehow resulting in the keycastr view being
offscreen or not visible. Sometimes changing the screen resolution can
help as it results in the settings being reset.

On Mon, Sep 5, 2016 at 6:54 PM, Sabastian notifications@github.com wrote:

Well, it does not work on OS X 10.11.6 as well... even I set the font size
to max.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/keycastr/keycastr/issues/25#issuecomment-244832174,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXHGC1GnmbUrvFuzaDMnkWakg2O1Zizks5qnMfSgaJpZM4EUJbw
.

<!-- gh-comment-id:245044982 --> @akitchen commented on GitHub (Sep 6, 2016): It works fine for me on that same version of OS X. This probably has more to do with your settings somehow resulting in the keycastr view being offscreen or not visible. Sometimes changing the screen resolution can help as it results in the settings being reset. On Mon, Sep 5, 2016 at 6:54 PM, Sabastian notifications@github.com wrote: > Well, it does not work on OS X 10.11.6 as well... even I set the font size > to max. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > https://github.com/keycastr/keycastr/issues/25#issuecomment-244832174, > or mute the thread > https://github.com/notifications/unsubscribe-auth/AAXHGC1GnmbUrvFuzaDMnkWakg2O1Zizks5qnMfSgaJpZM4EUJbw > .
Author
Owner

@massisenergy commented on GitHub (Oct 20, 2024):

Have you tried removing it from security and privacy, and re-adding it? Sometimes this is necessary in more recent versions of OS X when keycastr's settings have changed.

MacOS Sequoia 15.1, this suggestion worked for me!

<!-- gh-comment-id:2425059727 --> @massisenergy commented on GitHub (Oct 20, 2024): > Have you tried removing it from security and privacy, and re-adding it? Sometimes this is necessary in more recent versions of OS X when keycastr's settings have changed. > **MacOS Sequoia 15.1**, this suggestion worked for me!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/keycastr#24
No description provided.