unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: emacs-devel@gnu.org
Subject: Re: NS Port drawing, again
Date: Sat, 17 Nov 2018 10:22:10 +0000	[thread overview]
Message-ID: <20181117102210.GA66889@breton.holly.idiocy.org> (raw)
In-Reply-To: <m2in14b7hk.wl%esq@lawlist.com>

On Sat, Nov 10, 2018 at 07:47:35PM -0800, Keith David Bershatsky wrote:
> With respect to cursors being left behind when scrolling, I have dealt with that in playing with feature requests #22873 (multiple fake cursors) and #17684 (crosshairs) by removing the cursors at the outset of redisplay in various locations.  For example, see the locations where I have:
> 
>   mc_remove_multiple_cursors (w);
>   mc_remove_crosshairs (w);
> 
> See proof concept patch version 015 (11_10_2018__18_53_09_703.diff):

The problem we’re having with cursors is that when we ask for a cursor
to be removed it doesn’t actually happen on the bitmap until Cocoa
gets round to running drawRect. We can force it to run but that
invariably results in blank frames and things. On Mojave at least.

The current code works in most situations. There’s no longer any
random blanking of the screen (I think), so it’s perfectly usable, it
just has some weird issues with cursors. (I believe there are still
issues with the menus though? Nobody’s mentioned that for a while.)

I tried implementing drawing to a buffer, and that works perfectly on
High Sierra (except for some bits I know how to fix), but Aaron
reports that it doesn’t work at all on Mojave. I don’t know what I’ve
done wrong.

-- 
Alan Third



  reply	other threads:[~2018-11-17 10:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-11  3:47 NS Port drawing, again Keith David Bershatsky
2018-11-17 10:22 ` Alan Third [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-10-12  9:28 Alan Third

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=20181117102210.GA66889@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=emacs-devel@gnu.org \
    --cc=esq@lawlist.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).