Recovering and efficient development cycle for macOS app using NSEventTap
Recovering and efficient development cycle for macOS app using NSEventTap
- Subject: Recovering and efficient development cycle for macOS app using NSEventTap
- From: π via Accessibility-dev <email@hidden>
- Date: Mon, 22 Jul 2019 16:20:30 +0300
I am designing a keyboard assistive app. By nature this needs to intercept
and emit NSEvent-s.
With the original (four-year-old) Xcode project, every time I rebuilt I
would have to:
- run the project, whereupon `CGEventTapCreate` would fail
- SysPrefs -> Security&Privacy -> Privacy -> {uncheck and RE-check my app}
- run the project AGAIN
This quickly becomes very annoying.
A couple of weeks back I created the Xcode project from scratch using the
current version of Xcode. To my joy I found that I did not have to go
through this process.
I'm currently testing in Catalina beta / XCode 11 beta, and annoyingly the
original problem is back. Furthermore I have to fight my way through two
new dialogs:
- “x.app” Would Like to Access Speech Recognition
- “x.app” Would Like to Access the Microphone
(... likely corresponding to `Privacy - {Speech Recognition / Microphone}
Usage Description` in info.plist, both of which have been added recently).
This makes for a very clumsy development cycle. Can I cut some corners
here?
π
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden