From: Eli Zaretskii <eliz@gnu.org>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: emacs-devel@gnu.org
Subject: Re: Drawing dirty rectangles with expose_window: row->clip = fr
Date: Tue, 02 Apr 2019 19:51:49 +0300 [thread overview]
Message-ID: <83ftr0fize.fsf@gnu.org> (raw)
In-Reply-To: <m2wokc74ov.wl%esq@lawlist.com> (message from Keith David Bershatsky on Tue, 02 Apr 2019 09:27:44 -0700)
> Date: Tue, 02 Apr 2019 09:27:44 -0700
> From: Keith David Bershatsky <esq@lawlist.com>
> Cc: emacs-devel@gnu.org
>
> In this example, there is one frame with two windows in a top/bottom equal split. The top window (*scratch*) does not have any fake cursors. The bottom window (*MC-TEST*) does have fake cursors. It appears that expose_window is drawing the mode-line of the top window, and the rectangle extends down into the first line of the bottom window that has fake cursors. The fake cursors draw on the first line of the bottom window, but the glyphs do not draw on top of the box/hollow cursors. This happens at the section of expose_window where it has the comment:
>
> /* Display the mode line if there is one. */
I don't think I understand you answer.
What is the height of the mode line? is it 16 pixels or less? IOW,
how do you conclude that the rectangle 'fr' extends beyond the mode
line?
I also don't understand the meaning of this part:
The fake cursors draw on the first line of the bottom window, but
the glyphs do not draw on top of the box/hollow cursors.
Which glyphs "do not draw on top of the box/hollow cursors"?
next prev parent reply other threads:[~2019-04-02 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 16:27 Drawing dirty rectangles with expose_window: row->clip = fr Keith David Bershatsky
2019-04-02 16:51 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-03 19:28 Keith David Bershatsky
2019-04-02 20:42 Keith David Bershatsky
2019-04-02 17:42 Keith David Bershatsky
2019-04-02 1:55 Keith David Bershatsky
2019-04-02 14:48 ` Eli Zaretskii
2019-04-02 19:34 ` 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=83ftr0fize.fsf@gnu.org \
--to=eliz@gnu.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).