[GH-ISSUE #105] 'Toggle Capturing' hotkey disappears after switching tabs #87

Closed
opened 2026-05-05 04:53:01 -06:00 by gitea-mirror · 21 comments
Owner

Originally created by @szabolcsdombi on GitHub (Dec 1, 2017).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/105

Toggle capturing just disappeared and recording is bound to the key A that makes the app not usable.

Version: v0.9.5

image

Where is the config file located?

Originally created by @szabolcsdombi on GitHub (Dec 1, 2017). Original GitHub issue: https://github.com/keycastr/keycastr/issues/105 Toggle capturing just disappeared and recording is bound to the key `A` that makes the app not usable. Version: [v0.9.5](https://github.com/keycastr/keycastr/releases/download/v0.9.5/KeyCastr.app.zip) ![image](https://user-images.githubusercontent.com/11232402/33476661-66d1d952-d68b-11e7-962e-bb4507507a91.png) Where is the config file located?
gitea-mirror 2026-05-05 04:53:01 -06:00
Author
Owner

@akitchen commented on GitHub (Dec 5, 2017):

Thanks for reporting. Looks like there's a layout quirk in the latest macOS vs. that window's resizing behavior - I only see this after switching tabs, and I had to restart the app to get that field back.

The settings are stored in NSUserDefaults, so you're probably best off just restarting to get the text field back until this is fixed.

<!-- gh-comment-id:349189955 --> @akitchen commented on GitHub (Dec 5, 2017): Thanks for reporting. Looks like there's a layout quirk in the latest macOS vs. that window's resizing behavior - I only see this after switching tabs, and I had to restart the app to get that field back. The settings are stored in NSUserDefaults, so you're probably best off just restarting to get the text field back until this is fixed.
Author
Owner

@szabolcsdombi commented on GitHub (Dec 5, 2017):

  • deleted the keycastr from the Applications folder.
  • downloaded keycastr again.
  • moved keycastr from the Downloads to the Applications.
  • run keycastrs

Somehow the preferences remain.

keycastr

<!-- gh-comment-id:349209931 --> @szabolcsdombi commented on GitHub (Dec 5, 2017): - deleted the keycastr from the Applications folder. - downloaded keycastr again. - moved keycastr from the Downloads to the Applications. - run keycastrs Somehow the preferences remain. ![keycastr](https://user-images.githubusercontent.com/11232402/33593133-a5cd34b8-d996-11e7-82f7-91f243dab501.gif)
Author
Owner

@akitchen commented on GitHub (Dec 5, 2017):

It’s not clear from your screen recording - are you not able to change the ‘Toggle Capturing’ shortcut? I was able to change it on my machine without any issue.

On Dec 4, 2017, at 10:35 PM, Szabolcs Dombi notifications@github.com wrote:

deleted the keycastr from the Applications folder.
downloaded keycastr again.
moved keycastr from the Downloads to the Applications.
run keycastrs
Somehow the preferences remain.

https://user-images.githubusercontent.com/11232402/33593133-a5cd34b8-d996-11e7-82f7-91f243dab501.gif

You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/keycastr/keycastr/issues/105#issuecomment-349209931, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXHGF__CclPtFCFi4J-QvD1TRIiE6r_ks5s9OQbgaJpZM4QyFpv.

<!-- gh-comment-id:349359097 --> @akitchen commented on GitHub (Dec 5, 2017): It’s not clear from your screen recording - are you not able to change the ‘Toggle Capturing’ shortcut? I was able to change it on my machine without any issue. > On Dec 4, 2017, at 10:35 PM, Szabolcs Dombi <notifications@github.com> wrote: > > deleted the keycastr from the Applications folder. > downloaded keycastr again. > moved keycastr from the Downloads to the Applications. > run keycastrs > Somehow the preferences remain. > > <https://user-images.githubusercontent.com/11232402/33593133-a5cd34b8-d996-11e7-82f7-91f243dab501.gif> > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub <https://github.com/keycastr/keycastr/issues/105#issuecomment-349209931>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAXHGF__CclPtFCFi4J-QvD1TRIiE6r_ks5s9OQbgaJpZM4QyFpv>. >
Author
Owner

@szabolcsdombi commented on GitHub (Dec 5, 2017):

No, I am not.
It is A whatever I do.
Not sure how could I help resolving this :(
Does this happen to anyone else?

<!-- gh-comment-id:349435584 --> @szabolcsdombi commented on GitHub (Dec 5, 2017): No, I am not. It is `A` whatever I do. Not sure how could I help resolving this :( Does this happen to anyone else?
Author
Owner

@akitchen commented on GitHub (Dec 8, 2017):

I'm not sure how you got into this situation. Seems like there might be a bug in ShortcutRecorder (which provides the functionality here).

We'll look into updating it for the next release; meanwhile you may be able to use the defaults command in the terminal to fix the problem. For example, try running this in the terminal:

defaults read net.stephendeken.KeyCastr
and
man defaults for more info

<!-- gh-comment-id:350306242 --> @akitchen commented on GitHub (Dec 8, 2017): I'm not sure how you got into this situation. Seems like there might be a bug in ShortcutRecorder (which provides the functionality here). We'll look into updating it for the next release; meanwhile you may be able to use the `defaults` command in the terminal to fix the problem. For example, try running this in the terminal: `defaults read net.stephendeken.KeyCastr` and `man defaults` for more info
Author
Owner

@szabolcsdombi commented on GitHub (Dec 8, 2017):

thank you!

<!-- gh-comment-id:350331861 --> @szabolcsdombi commented on GitHub (Dec 8, 2017): thank you!
Author
Owner

@jachacha commented on GitHub (Feb 19, 2019):

Hi there,
I'v run into the same issue. Could you please describe more in dept how to use the defaults command in the terminal to fix the problem?
I am using the latest version: v0.9.6
Thank you.

<!-- gh-comment-id:464996462 --> @jachacha commented on GitHub (Feb 19, 2019): Hi there, I'v run into the same issue. Could you please describe more in dept how to use the defaults command in the terminal to fix the problem? I am using the latest version: v0.9.6 Thank you.
Author
Owner

@martin-martin commented on GitHub (Mar 2, 2019):

The default key seems to set itself to this when it gets stuck:

capturingHotKey = <00000000 00000000>;

See my full output from running defaults read net.stephendeken.KeyCastr:

{
    "NSWindow Frame KCBezelWindow default.bezelWindow" = "10 10 1440 100 0 0 1440 877 ";
    SUEnableAutomaticChecks = 0;
    SUHasLaunchedBefore = 1;
    SULastCheckTime = "2019-03-02 16:06:08 +0000";
    SUSendProfileInfo = 0;
    capturingHotKey = <00000000 00000000>;
    "default.commandKeysOnly" = 0;
    "default.fadeDelay" = "0.2243193069306927";
    "default.fadeDuration" = "0.08113010817825204";
    "default.fontSize" = "17.55167079207919";
    displayIcon = 1;
    selectedVisualizer = Default;
}

Maybe this can be helpful.

For me, restarting the app helped to be able to make it possible to change the toggle command again.

<!-- gh-comment-id:468935375 --> @martin-martin commented on GitHub (Mar 2, 2019): The default key seems to set itself to this when it gets stuck: ```capturingHotKey = <00000000 00000000>;``` See my full output from running `defaults read net.stephendeken.KeyCastr`: ``` { "NSWindow Frame KCBezelWindow default.bezelWindow" = "10 10 1440 100 0 0 1440 877 "; SUEnableAutomaticChecks = 0; SUHasLaunchedBefore = 1; SULastCheckTime = "2019-03-02 16:06:08 +0000"; SUSendProfileInfo = 0; capturingHotKey = <00000000 00000000>; "default.commandKeysOnly" = 0; "default.fadeDelay" = "0.2243193069306927"; "default.fadeDuration" = "0.08113010817825204"; "default.fontSize" = "17.55167079207919"; displayIcon = 1; selectedVisualizer = Default; } ``` Maybe this can be helpful. For me, restarting the app helped to be able to make it possible to change the toggle command again.
Author
Owner

@martin-martin commented on GitHub (Mar 2, 2019):

Hi there,
I'v run into the same issue. Could you please describe more in dept how to use the defaults command in the terminal to fix the problem?
I am using the latest version: v0.9.6
Thank you.

From man defaults:

write domain key 'value'
  Writes value as the value for key in domain.  value must be a property list, and must
  be enclosed in single quotes.  For example:

        defaults write com.companyname.appname "Default Color" '(255, 0, 0)'

  sets the value for Default Color to an array containing the strings 255, 0, 0 (the red,
  green, and blue components). Note that the key is enclosed in quotation marks because
  it contains a space.

That means that typing:

defaults write net.stephendeken.KeyCastr capturingHotKey '<00001200 08000000>'

should change the shortcut to cmd + shift + c! Hope this helps @jachacha ! :)

<!-- gh-comment-id:468935694 --> @martin-martin commented on GitHub (Mar 2, 2019): > Hi there, > I'v run into the same issue. Could you please describe more in dept how to use the defaults command in the terminal to fix the problem? > I am using the latest version: v0.9.6 > Thank you. From `man defaults`: ``` write domain key 'value' Writes value as the value for key in domain. value must be a property list, and must be enclosed in single quotes. For example: defaults write com.companyname.appname "Default Color" '(255, 0, 0)' sets the value for Default Color to an array containing the strings 255, 0, 0 (the red, green, and blue components). Note that the key is enclosed in quotation marks because it contains a space. ``` That means that typing: ```bash defaults write net.stephendeken.KeyCastr capturingHotKey '<00001200 08000000>' ``` should change the shortcut to `cmd + shift + c`! Hope this helps @jachacha ! :)
Author
Owner

@jachacha commented on GitHub (Mar 6, 2019):

Hi Martin,
thanks a lot, this really helped, now I have the shortcut at least set to something that wouldn't turn the recording on and off all the time. Is there a way how to disable the hotkey at all?
Cheers,
Jarka

<!-- gh-comment-id:469954126 --> @jachacha commented on GitHub (Mar 6, 2019): Hi Martin, thanks a lot, this really helped, now I have the shortcut at least set to something that wouldn't turn the recording on and off all the time. Is there a way how to disable the hotkey at all? Cheers, Jarka
Author
Owner

@luckman212 commented on GitHub (Oct 28, 2019):

This issue still persists on v0.9.8 + Catalina 10.15
The only way to get that field back is to quit the app and relaunch it

image

<!-- gh-comment-id:546955955 --> @luckman212 commented on GitHub (Oct 28, 2019): This issue still persists on v0.9.8 + Catalina 10.15 The only way to get that field back is to quit the app and relaunch it ![image](https://user-images.githubusercontent.com/1992842/67683919-9dbf8480-f968-11e9-942b-9f07aa20350c.png)
Author
Owner

@jqhan commented on GitHub (Nov 27, 2019):

If you can't get the app to work on Mojave 10.14.6, you might want to try to use an old release version, v0.9.6 etc, if you want the app to be usable. Note that you might have to deal with the Accessibility API problem for this approach, which is discussed in this issue

<!-- gh-comment-id:559072450 --> @jqhan commented on GitHub (Nov 27, 2019): If you can't get the app to work on Mojave 10.14.6, you might want to try to use an old release version, v0.9.6 etc, if you want the app to be usable. Note that you might have to deal with the Accessibility API problem for this approach, which is discussed in [this issue](https://github.com/keycastr/keycastr/issues/146)
Author
Owner

@akitchen commented on GitHub (Nov 30, 2019):

The latest build works fine on Mojave, but Mojave seems a little quirky when it comes to accessibility API permissions. As much as I hate to say it, rebooting seemed to help.

<!-- gh-comment-id:560006919 --> @akitchen commented on GitHub (Nov 30, 2019): The latest build works fine on Mojave, but Mojave seems a little quirky when it comes to accessibility API permissions. As much as I hate to say it, [rebooting seemed to help](https://github.com/keycastr/keycastr/issues/146#issuecomment-553784800).
Author
Owner

@akitchen commented on GitHub (Nov 30, 2019):

As to this issue, it's somewhere between our very old build of ShortcutRecorder and KeyCastr's antique MainMenu.nib. Ultimately we need to update ShortcutRecorder and possibly rebuild the nib if we want to be able to edit it in a modern Xcode.

<!-- gh-comment-id:560007601 --> @akitchen commented on GitHub (Nov 30, 2019): As to this issue, it's somewhere between our very old build of ShortcutRecorder and KeyCastr's antique `MainMenu.nib`. Ultimately we need to update ShortcutRecorder and possibly rebuild the nib if we want to be able to edit it in a modern Xcode.
Author
Owner

@jsphkm commented on GitHub (Apr 11, 2020):

I'm using KeyCastr 0.9.8 on macOS Catalina 10.15.4, and can confirm that this issue persists. How do you remove the "A" shortcut from toggling?

<!-- gh-comment-id:612336717 --> @jsphkm commented on GitHub (Apr 11, 2020): I'm using KeyCastr 0.9.8 on macOS Catalina 10.15.4, and can confirm that this issue persists. How do you remove the "A" shortcut from toggling?
Author
Owner

@marq5 commented on GitHub (Apr 30, 2020):

Hi there,
I'v run into the same issue. Could you please describe more in dept how to use the defaults command in the terminal to fix the problem?
I am using the latest version: v0.9.6
Thank you.

From man defaults:

write domain key 'value'
  Writes value as the value for key in domain.  value must be a property list, and must
  be enclosed in single quotes.  For example:

        defaults write com.companyname.appname "Default Color" '(255, 0, 0)'

  sets the value for Default Color to an array containing the strings 255, 0, 0 (the red,
  green, and blue components). Note that the key is enclosed in quotation marks because
  it contains a space.

That means that typing:

defaults write net.stephendeken.KeyCastr capturingHotKey '<00001200 08000000>'

should change the shortcut to cmd + shift + c! Hope this helps @jachacha ! :)

Hi,

The terminal script changed the shortcut on my German localized user profile but didn't affect my English localized user profile. For my English user (on the same MBP Catalina) the shortcut is still "A" and can't be changed. Is that kind of strange or what?

<!-- gh-comment-id:621767388 --> @marq5 commented on GitHub (Apr 30, 2020): > > Hi there, > > I'v run into the same issue. Could you please describe more in dept how to use the defaults command in the terminal to fix the problem? > > I am using the latest version: v0.9.6 > > Thank you. > > From `man defaults`: > > ``` > write domain key 'value' > Writes value as the value for key in domain. value must be a property list, and must > be enclosed in single quotes. For example: > > defaults write com.companyname.appname "Default Color" '(255, 0, 0)' > > sets the value for Default Color to an array containing the strings 255, 0, 0 (the red, > green, and blue components). Note that the key is enclosed in quotation marks because > it contains a space. > ``` > > That means that typing: > > ```shell > defaults write net.stephendeken.KeyCastr capturingHotKey '<00001200 08000000>' > ``` > > should change the shortcut to `cmd + shift + c`! Hope this helps @jachacha ! :) Hi, The terminal script changed the shortcut on my German localized user profile but didn't affect my English localized user profile. For my English user (on the same MBP Catalina) the shortcut is still "A" and can't be changed. Is that kind of strange or what?
Author
Owner

@chrisman commented on GitHub (Jul 17, 2020):

Currently working through this issue with v0.9.8 obtained with brew cask install keycastr on Catalina 10.15.4.

Looks as though the defaults are now at io.github.keycastr.

That is, you can see the defaults with defaults read io.github.keycastr

~> defaults read io.github.keycastr
{
    "NSWindow Frame KCBezelWindow default.bezelWindow" = "10 10 1440 100 0 0 1440 900 ";
    SUEnableAutomaticChecks = 1;
    SUHasLaunchedBefore = 1;
    SULastCheckTime = "2020-07-17 19:29:48 +0000";
    SUSendProfileInfo = 0;
    capturingHotKey = {length = 8, bytes = 0x0000020032000000};
    "default.fontSize" = "64.63567450495049";
    displayIcon = 1;
    selectedVisualizer = Default;
}

Can anybody point me toward any documentation on the capturingHotKey format? It looks to no longer be in the format of <00001200 08000000>. I looked through man defaults and did a quick ddg but didn't see anything helpful.

<!-- gh-comment-id:660305043 --> @chrisman commented on GitHub (Jul 17, 2020): Currently working through this issue with v0.9.8 obtained with `brew cask install keycastr` on Catalina 10.15.4. Looks as though the defaults are now at io.github.keycastr. That is, you can see the defaults with `defaults read io.github.keycastr` ``` ~> defaults read io.github.keycastr { "NSWindow Frame KCBezelWindow default.bezelWindow" = "10 10 1440 100 0 0 1440 900 "; SUEnableAutomaticChecks = 1; SUHasLaunchedBefore = 1; SULastCheckTime = "2020-07-17 19:29:48 +0000"; SUSendProfileInfo = 0; capturingHotKey = {length = 8, bytes = 0x0000020032000000}; "default.fontSize" = "64.63567450495049"; displayIcon = 1; selectedVisualizer = Default; } ``` Can anybody point me toward any documentation on the `capturingHotKey` format? It looks to no longer be in the format of `<00001200 08000000>`. I looked through `man defaults` and did a quick ddg but didn't see anything helpful.
Author
Owner

@akitchen commented on GitHub (Jan 21, 2021):

This is fixed on the main branch as a part of the MainMenu.nib modernizations in v0.9.10, coming soon™

<!-- gh-comment-id:764785749 --> @akitchen commented on GitHub (Jan 21, 2021): This is fixed on the main branch as a part of the MainMenu.nib modernizations in v0.9.10, coming soon™
Author
Owner

@nicanordlc commented on GitHub (Jul 9, 2021):

I want to change the a key to other like option/alt so when I'm writing it does not activate and deactivate :/

This issue is still happening:

image

image

<!-- gh-comment-id:876881983 --> @nicanordlc commented on GitHub (Jul 9, 2021): I want to change the a key to other like option/alt so when I'm writing it does not activate and deactivate :/ This issue is still happening: ![image](https://user-images.githubusercontent.com/12496574/125018005-3bc28800-e042-11eb-8cee-0c8faeb82b1f.png) ![image](https://user-images.githubusercontent.com/12496574/125018035-454bf000-e042-11eb-853d-0b33e2aaa61a.png)
Author
Owner

@Arvidchen commented on GitHub (Dec 24, 2021):

Hello,

the issue still persists on Big Sur 11.6

I am running on a german keyboard. But i can´t change the CaptureKey. It isn´t displayed at all.

Besides the tool works great! Many thanks!

my defaults:
{
"NSWindow Frame KCBezelWindow default.bezelWindow" = "10 10 3420 145 0 0 3440 1415 ";
"NSWindow Frame svelte visualizerFrame" = "4 5 200 100 0 0 3440 1415 ";
SUEnableAutomaticChecks = 1;
SUHasLaunchedBefore = 1;
SULastCheckTime = "2021-12-24 15:04:30 +0000";
SUSendProfileInfo = 0;
capturingHotKey = {length = 8, bytes = 0x0000020029000000};
"default.commandKeysOnly" = 0;
"default.fontSize" = "49.50144230769231";
displayIcon = 1;
selectedVisualizer = Default;
}

EDIT:
Due to some random approaching my fingers on my keyboard it worked...
But thats not the "right" way i assume..

Merry Christmas
Arvid

<!-- gh-comment-id:1000869973 --> @Arvidchen commented on GitHub (Dec 24, 2021): Hello, the issue still persists on Big Sur 11.6 I am running on a german keyboard. But i can´t change the CaptureKey. It isn´t displayed at all. Besides the tool works great! Many thanks! my defaults: { "NSWindow Frame KCBezelWindow default.bezelWindow" = "10 10 3420 145 0 0 3440 1415 "; "NSWindow Frame svelte visualizerFrame" = "4 5 200 100 0 0 3440 1415 "; SUEnableAutomaticChecks = 1; SUHasLaunchedBefore = 1; SULastCheckTime = "2021-12-24 15:04:30 +0000"; SUSendProfileInfo = 0; capturingHotKey = {length = 8, bytes = 0x0000020029000000}; "default.commandKeysOnly" = 0; "default.fontSize" = "49.50144230769231"; displayIcon = 1; selectedVisualizer = Default; } **EDIT:** Due to some random approaching my fingers on my keyboard it worked... But thats not the "right" way i assume.. Merry Christmas Arvid
Author
Owner

@austinfinnql commented on GitHub (Feb 2, 2024):

I am using version 0.9.16 on Sonoma 14.1 and I just came across the issue. Does anyone have any suggestions on how to change the stop/start value to some random collection of characters (so it never switches off)

  • UPDATE: I can now change the stop/start command. It was a UX issue
  • As the example/default command Keycastr uses to stop/start casting was just the letter "A", I assumed the "Toggle capturing" field was a textfield, it isn't. I was pressing keys on my keyboard and, as far as I was concerned, nothing was happening i.e. I thought keycastr had a bug
  • For anyone who has the same issue, to change the stop/start command, go to preferences -> click on the "Toggle capturing" field -> hold the ⌘ button and then press the key you want to use to stop/start casting. See video below
  • If the example/default command kyecastr used was something like "⌘y", or some other command combination that is infrequently used, then it might reduce the confusion. Or if the "Toggle capturing" field was changed to a text field, it might also be another way to improve UX/reduce confusion

https://github.com/keycastr/keycastr/assets/30303430/5ac4e0fa-9640-4db2-9abe-78a875ff7fab

<!-- gh-comment-id:1922532140 --> @austinfinnql commented on GitHub (Feb 2, 2024): ~I am using version 0.9.16 on Sonoma 14.1 and I just came across the issue. Does anyone have any suggestions on how to change the stop/start value to some random collection of characters (so it never switches off)~ - UPDATE: I can now change the stop/start command. It was a UX issue - As the example/default command Keycastr uses to stop/start casting was just the letter "A", I assumed the "Toggle capturing" field was a textfield, it isn't. I was pressing keys on my keyboard and, as far as I was concerned, nothing was happening i.e. I thought keycastr had a bug - For anyone who has the same issue, to change the stop/start command, go to preferences -> click on the "Toggle capturing" field -> hold the ⌘ button and then press the key you want to use to stop/start casting. See video below - If the example/default command kyecastr used was something like "⌘y", or some other command combination that is infrequently used, then it might reduce the confusion. Or if the "Toggle capturing" field was changed to a text field, it might also be another way to improve UX/reduce confusion https://github.com/keycastr/keycastr/assets/30303430/5ac4e0fa-9640-4db2-9abe-78a875ff7fab
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#87
No description provided.