all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: David Hart <david@iamdavidhart.com>
Cc: iqgrande@gmail.com, 34213@debbugs.gnu.org
Subject: bug#34213: 27.0.50; Menu bar requires 2 clicks, is unresponsive, or has delays on macOS Mojave
Date: Mon, 6 Apr 2020 19:54:08 +0100	[thread overview]
Message-ID: <20200406185408.GA44546@breton.holly.idiocy.org> (raw)
In-Reply-To: <CAOcguANxY8KohTVxs+mob0wBNNCPr0RXcOYzQV_xCiQs=11h2A@mail.gmail.com>

On Mon, Apr 06, 2020 at 03:19:25AM -0700, David Hart wrote:
> The mechanism used in the ns port of emacs to cancel menu tracking, and to
> post a CGEvent to resume it after menus have been updated via lisp no
> longer works on recent macOS versions.
> 
> The cause of this bug is due to Apple tightening security in macOS, and no
> longer allowing apps to post arbitrary CGEvents to the system.
> 
> You can observe a console message on macOS Catalina when the first click
> fails: "Sender is prohibited from synthesizing events".
> 
> A proposed fix is included inline below, using a newer API
> 'CGEventPostToPid' instead of CGEventPost. The newer API accepts a pid
> specifying the recipient, and when the recipient is the same pid as the
> sending process, the event gets posted successfully.

Hi, thanks for looking into this. Unfortunately your fix doesn’t work
for me here on macOS 10.14.

Which version of macOS did you test it on?
-- 
Alan Third





  reply	other threads:[~2020-04-06 18:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26 22:14 bug#34213: 27.0.50; Menu bar requires 2 clicks, is unresponsive, or has delays on macOS Mojave Anthony Michael Agelastos
2019-01-30 19:57 ` Alan Third
2020-04-06 10:19 ` David Hart
2020-04-06 18:54   ` Alan Third [this message]
2020-09-30 15:42     ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200406185408.GA44546@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=34213@debbugs.gnu.org \
    --cc=david@iamdavidhart.com \
    --cc=iqgrande@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.