[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#44333: 27.1; macOS menu bar 2-clicks
From: |
Mattias Engdegård |
Subject: |
bug#44333: 27.1; macOS menu bar 2-clicks |
Date: |
Sun, 1 Nov 2020 11:50:32 +0100 |
31 okt. 2020 kl. 16.01 skrev Alan Third <alan@idiocy.org>:
> IIRC the problem is due to the reposting of the menu click event so
> the menu can be populated when lisp is running. The Mac port doesn't
> have this problem most probably because it's a completely different
> architecture but it has the GUI and lisp parts split into two separate
> threads which is one way I can see of fixing this.
Last time I looked it seemed that the Mac port actually did synthesise events
but used some other means (Carbon?), but I may be wrong.
> If anyone else has a simpler solution I'd love to hear it.
Maybe we are overthinking it. I don't think the Cocoa event loop really is
running in a different thread. Anecdotal evidence (printf!) indicates that it
isn't.
(https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32864#38 has a previous
investigation into the matter.)
I just did the simplest thing possible and it works (with a slight latency at
times, but perhaps tolerable). I'd like to know what's wrong with running Lisp
in the event loop. It does appear safe to me.
macos-1-click-menu-bar.diff
Description: Binary data
- bug#44333: 27.1; macOS menu bar 2-clicks,
Mattias Engdegård <=