mirror of
https://github.com/keycastr/keycastr.git
synced 2026-05-15 14:15:50 -06:00
[GH-ISSUE #252] Not working in macOS Ventura #216
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#216
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 @rogeruiz on GitHub (Nov 11, 2022).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/252
hi @akitchen I've tried these steps you've outlined with macOS Ventura. I can't seem to get Keycastr working though.
=> Steps you've outlined in #222 (https://github.com/keycastr/keycastr/issues/222#issuecomment-1008110225)
I'd also like to submit a Ventura specific screenshot and documentation PR eventually to help out too since it looks like it'll be needed since Apple changed System Preferences to System Settings in Ventura.
Also, I'll submit a PR with the changes you mentioned in your message separately for folks who aren't on Ventura yet.
system info
MacBook Pro 16-inch, 2019
macOS 13.0 (22A380)
@rogeruiz commented on GitHub (Nov 11, 2022):
I found the Wiki, and then tried looking for the Enable access for assistive devices in the Apple Support documentation for Ventura and haven't found anything yet.
=> Welcome to the keycastr wiki!
It looks like it might be covered under the Accessibility section of the new System Settings under Privacy and Security. This leads me to believe maybe there's an issue with the code.
=> Change Keyboard settings for accessibility on Mac
=> Change Accessibility settings on Mac
I have the project checked out and am going to take a look at the source to see if there is some kind of error or bug that I am not seeing from
the runningcompiling the application.@akitchen commented on GitHub (Nov 11, 2022):
Hello and thank you for opening an issue and accompanying PR!
The wiki is something I haven't paid attention to in a long time, thanks for mentioning that. Will need to give it a bit more thought since it's Yet Another Thing that would need to be kept up to date.
Sorry to hear about the issues with Ventura. Unfortunately I'm not able to run it on my main machine yet but I do have it in a VM. I will try to take a look soon, and of course any further PRs are welcome if you discover anything while looking into the code yourself.
@akitchen commented on GitHub (Nov 15, 2022):
So, I was able to run the current build of KeyCastr in a Ventura VM. It may have had a delay in initializing itself in the user defaults since it didn't seem to work at first, but I switched on the mouse visualizer and it worked, and when I switched over to Svelte it worked too. And then when switching back to the Default visualizer it worked OK from there on out.
I'm still on a beta release of Ventura and for some reason resetting the user defaults doesn't seem to work so I can't reset my state and do it again. However, I do think this issue is recoverable if you switch to the Svelte visualizer and then back to Default. Give it a try and let us know!
It's also possible that re-compiling keycastr as-is (when I get to the next release) will pick up other implicit fixes and improvements in the macOS SDKs but again, I was able to get the current build to run OK.
@rogeruiz commented on GitHub (Nov 15, 2022):
ah interesting. okay. so I'm going to revert all my changes in work in progress branch and see if it clears up my fixes. I'll try to re-compile it for myself. thanks for the update. I am still learning Xcode development.
@rogeruiz commented on GitHub (Nov 17, 2022):
Closing this as described in #254
@skymagician commented on GitHub (Feb 27, 2023):
not working