From: Keith David Bershatsky <esq@lawlist.com>
To: Alan Third <alan@idiocy.org>
Cc: emacs-devel@gnu.org
Subject: Re: nsterm.m: How to prevent _inactive_ window update from overreaching.
Date: Sat, 24 Nov 2018 18:20:34 -0800 [thread overview]
Message-ID: <m21s79zyml.wl%esq@lawlist.com> (raw)
Thank you, Alan, for pointing me in the right direction.
I will continue working on this project in my spare time.
Keith
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> Date: [11-22-2018 14:57:20] <22 Nov 2018 22:57:20 +0000>
> From: Alan Third <alan@idiocy.org>
> To: Keith David Bershatsky <esq@lawlist.com>
> Cc: Emacs Devel <emacs-devel@gnu.org>
> Subject: Re: nsterm.m: How to prevent _inactive_ window update from overreaching.
>
> * * *
>
> There are two (potential) issues here:
>
> 1. Something is marking a large portion of the frame as dirty, and
> it's overflowing from the left window to the right, probably all the
> way to the right edge of the frame. That's almost certainly a call to
> ns_clip_to_rect.
>
> 2. When the right window is marked as dirty it's failing to redraw
> completely. I'd assume what is happening is that the expose_frame
> functions (and its descendants) don't notice that the crosshair needs
> to be redrawn. I'm unsure how that side of it works, something must
> have to compare the rectangle to be exposed with the contents of the
> frame and decide what needs redrawn.
>
> IMHO both should be fixed. 1 because it's redrawing too much, and 2
> because there are other circumstances where part of your crosshair
> could be marked as dirty and therefore need redrawn.
>
> --
> Alan Third
next reply other threads:[~2018-11-25 2:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-25 2:20 Keith David Bershatsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-12 7:07 nsterm.m: How to prevent _inactive_ window update from overreaching Keith David Bershatsky
2018-11-29 5:52 Keith David Bershatsky
2018-11-27 4:58 Keith David Bershatsky
2018-11-28 21:31 ` Alan Third
2018-11-26 2:14 Keith David Bershatsky
2018-11-26 20:09 ` Alan Third
2018-11-22 20:13 Keith David Bershatsky
2018-11-22 19:07 Keith David Bershatsky
2018-11-22 22:57 ` 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=m21s79zyml.wl%esq@lawlist.com \
--to=esq@lawlist.com \
--cc=alan@idiocy.org \
--cc=emacs-devel@gnu.org \
/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).