From: "Jan D." <jan.h.d@swipnet.se>
To: Dmitry Antipov <dmantipov@yandex.ru>, martin rudalics <rudalics@gmx.at>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: GTK scroll bar artifacts [Was: Re: GTK scroll bar question]
Date: Thu, 31 Jul 2014 17:03:40 +0200 [thread overview]
Message-ID: <53DA5ACC.4040607@swipnet.se> (raw)
In-Reply-To: <53DA50B0.7040606@yandex.ru>
Dmitry Antipov skrev 2014-07-31 16:20:
> On 07/30/2014 04:39 PM, martin rudalics wrote:
>
>> I suppose it's related to changes in GTK3. I often see this:
>>
>> http://lists.gnu.org/archive/html/emacs-devel/2014-01/msg02228.html
>>
>> And there's also bug#17982.
>
> From GTK3's gtkeventbox.c:
>
> * You should generally make your event box invisible if
> * you just want to trap events. Creating a visible window
> * may cause artifacts that are visible to the user, especially
> * if the user is using a theme with gradients or pixmaps.
>
> This helps in my case. OK to install?
No. The reason for having the event box is to have a window to draw
into, not to trap events. If you make it invisible, there will be no
window to draw into and the scroll bar will draw into the parent window,
which is what we don't want. Since Emacs draws and clears the window
with X calls, the scroll bar does not know it should redraw itself,
leading to all kind of races.
Jan D.
prev parent reply other threads:[~2014-07-31 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 11:11 GTK scroll bar question Dmitry Antipov
2014-07-30 12:39 ` martin rudalics
2014-07-30 15:38 ` Dmitry Antipov
2014-07-30 18:30 ` Jan Djärv
2014-07-31 5:05 ` Dmitry Antipov
2014-07-31 6:52 ` Jan D.
2014-07-31 10:19 ` Dmitry Antipov
2014-07-31 11:53 ` Jan Djärv
2014-07-31 15:13 ` Dmitry Antipov
2014-07-31 15:27 ` Jan D.
2014-07-31 14:20 ` GTK scroll bar artifacts [Was: Re: GTK scroll bar question] Dmitry Antipov
2014-07-31 15:03 ` Jan D. [this message]
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=53DA5ACC.4040607@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=dmantipov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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.