all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mustafa Kocaturk <murskt@gmail.com>
To: 21662@debbugs.gnu.org
Cc: steve@sanityinc.com
Subject: bug#21662: 25.0.50; visible-bell causes display artifacts on OS X 10.11
Date: Tue, 13 Oct 2015 21:13:25 -0500	[thread overview]
Message-ID: <B8112AB9-6BAD-4429-B916-4073275405A6@gmail.com> (raw)
In-Reply-To: <m2lhbagjha.fsf@sanityinc.com>

Hi,

The current implementation of the visual bell on NextStep is to cache and redraw a rectangle on the current Emacs frame *from outside the NextStep run loop*. It seems this was good enough so far but is no longer a particularly supported one for the latest Mac OS X version.
Maintaining it might still be possible, only with sufficient effort and caution.

Alternative: Switch to an implementation that is particularly supported in this release of OS X, as follows:
Create a temporary NSView object and attach it to the selected EmacsView object.
This new subview draws itself, starts an NSTimer, with a callback in the current NS run loop. 
When the timer expires the callback is entered, which updates, hides, and finally removes the subview from its superview.
The view is garbage collected, all as part of the NS run loop. 
The required change is small: Add a NSView-derived class in nsterm.m and replace old cache/draw/restore code with new temporary local instance of this new class.

Best regards,
Mustafa






  parent reply	other threads:[~2015-10-14  2:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-11  3:41 bug#21662: 25.0.50; visible-bell causes display artifacts on OS X 10.11 Steve Purcell
2015-10-11 14:31 ` Spike Ilacqua
2015-10-14  2:13 ` Mustafa Kocaturk [this message]
2015-10-22 14:41 ` Mustafa Kocaturk
2015-10-22 16:07   ` Mustafa Kocaturk
2015-11-18 20:27 ` bug#21662: " Anders Lindgren
2015-11-21 20:05   ` Anders Lindgren
2015-11-23 22:09 ` bug#21662: Fixed Anders Lindgren

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=B8112AB9-6BAD-4429-B916-4073275405A6@gmail.com \
    --to=murskt@gmail.com \
    --cc=21662@debbugs.gnu.org \
    --cc=steve@sanityinc.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.