Hello World!
I've been finally able to make the jump from legacy hardware (with macOS 10.14) to Big Sur, and even though I'm a Big Fan mostly, I quite dislike a particular problem this has caused me.
Like the title says, I make use of IOKit's IOHIDManager interface to receive user inputs. I've used that mostly for game controller inputs and raw mouse movement, but also liked how I'm able to address multiple keyboards and mice independently this way. This is mostly done in C++, so no (direct) access to higher-level APIs.
With Big Sur (or Catalina, as far as I'm aware) the user is now prompted to explicitly allow my app to receive keystrokes from all processes as soon as I call IOHIDManagerOpen.
That's not my complaint, in fact I agree with macOS, the user should be prompted about this! My problem however is that I'm not interested in what the user is being warned here.
I can already guess the answer, but is there a way to avoid this breach of security using the IOHID interfaces and therefore prevent macOS to bother (and possibly scare) the user?
I'm aware of Apple's Game Controller framework, but it's difficult to use this while also supporting earlier macOS versions.
Many thanks in advance!
I've been finally able to make the jump from legacy hardware (with macOS 10.14) to Big Sur, and even though I'm a Big Fan mostly, I quite dislike a particular problem this has caused me.
Like the title says, I make use of IOKit's IOHIDManager interface to receive user inputs. I've used that mostly for game controller inputs and raw mouse movement, but also liked how I'm able to address multiple keyboards and mice independently this way. This is mostly done in C++, so no (direct) access to higher-level APIs.
With Big Sur (or Catalina, as far as I'm aware) the user is now prompted to explicitly allow my app to receive keystrokes from all processes as soon as I call IOHIDManagerOpen.
That's not my complaint, in fact I agree with macOS, the user should be prompted about this! My problem however is that I'm not interested in what the user is being warned here.
I can already guess the answer, but is there a way to avoid this breach of security using the IOHID interfaces and therefore prevent macOS to bother (and possibly scare) the user?
I'm aware of Apple's Game Controller framework, but it's difficult to use this while also supporting earlier macOS versions.
Many thanks in advance!