With this PR, an additional error message is logged/shown if the Input Monitoring permission is not granted on macOS. A message about this is already emitted when requesting the permission, but this happens before the UI is initialized and will therefore not be displayed to the user (except in the terminal and log file).
@oktal3700 Any idea on how we could avoid logging this twice? The keyboard initialization happens in the CInputManager which again is initialized by CApplication which AFAIK should be UI independent. In the future maybe some mechanism should be added to show error messages in the early initialization phase.
Related to #125
With this PR, an additional error message is logged/shown if the Input Monitoring permission is not granted on macOS. A message about this is already emitted when requesting the permission, but this happens before the UI is initialized and will therefore not be displayed to the user (except in the terminal and log file).
@oktal3700 Any idea on how we could avoid logging this twice? The keyboard initialization happens in the
CInputManagerwhich again is initialized byCApplicationwhich AFAIK should be UI independent. In the future maybe some mechanism should be added to show error messages in the early initialization phase.