From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: 15398@debbugs.gnu.org, Serge Kosyrev <skosyrev@ptsecurity.ru>,
Samium Gromoff <_deepfire@feelingofgreen.ru>
Subject: bug#15398: 24.3; Frame redraw completely screwed
Date: Fri, 20 Sep 2013 11:32:11 +0200 [thread overview]
Message-ID: <7AFCA8AA-81E8-49DA-AFD9-FA1F91EBA664@swipnet.se> (raw)
In-Reply-To: <523C00AE.1020108@yandex.ru>
Hello.
20 sep 2013 kl. 10:00 skrev Dmitry Antipov <dmantipov@yandex.ru>:
> On 09/20/2013 10:47 AM, Jan Djärv wrote:
>
>> 20 sep 2013 kl. 05:41 skrev Dmitry Antipov <dmantipov@yandex.ru>:
>>
>>> On 09/19/2013 08:41 PM, Jan Djärv wrote:
>>>
>>>> I don't recall all the details, but I think the comment actually means "for GTK 2.6 and newer".
>>>
>>> Ugh. Reverted in r114402 (for visible frames; in general, I think
>>> that it is possible to handle Expose events a bit more intelligently).
>>
>> Not as long as we do pure X-calls on Gtk-widgets.
>
> Yes, mixing Xlib and Gtk is ugly. But I would like to get your comments on this first
> (also I'm looking for brave testers).
>
> Dmitry
>
> <gtk_clear_expose.patch>
This simply does not work. It assumes there is only one frame per root window, which is wrong.
It assumes Emacs will get Unmap events when something obscuring it goes away, this is wrong (other applications may cover Emacs and the go away).
Any optimization attempt in this area is futile, it will lead to errors for a very small performance benefit. The time is better spent into doing a proper double buffer solution.
Jan D.
next prev parent reply other threads:[~2013-09-20 9:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 19:48 bug#15398: 24.3; Frame redraw completely screwed Samium Gromoff
2013-09-16 20:53 ` Jan Djärv
2013-09-17 6:19 ` bug#15398: UNS: " Samium Gromoff
2013-09-17 7:23 ` Eli Zaretskii
2013-09-17 18:50 ` Jan Djärv
2013-09-17 21:17 ` bug#15398: UNS: " Samium Gromoff
2013-09-18 6:27 ` Eli Zaretskii
2013-09-18 21:07 ` Samium Gromoff
2013-09-19 6:50 ` Eli Zaretskii
2013-09-19 8:05 ` martin rudalics
2013-09-19 8:10 ` Eli Zaretskii
2013-09-19 8:27 ` martin rudalics
2013-09-19 8:53 ` Eli Zaretskii
2013-09-19 9:25 ` martin rudalics
2013-09-19 9:31 ` Eli Zaretskii
2013-09-19 10:58 ` martin rudalics
2013-09-19 13:04 ` Eli Zaretskii
2013-09-19 14:03 ` martin rudalics
2013-09-19 14:20 ` Eli Zaretskii
2013-09-19 14:24 ` martin rudalics
2013-09-19 16:17 ` Glenn Morris
2013-09-19 17:06 ` martin rudalics
2013-09-19 14:04 ` Stefan Monnier
2013-09-19 14:21 ` martin rudalics
2013-09-19 14:54 ` Serge Kosyrev
2013-09-19 16:41 ` Jan Djärv
2013-09-20 3:41 ` Dmitry Antipov
2013-09-20 6:47 ` Jan Djärv
2013-09-20 8:00 ` Dmitry Antipov
2013-09-20 9:32 ` Jan Djärv [this message]
2020-09-09 13:24 ` Lars Ingebrigtsen
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=7AFCA8AA-81E8-49DA-AFD9-FA1F91EBA664@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=15398@debbugs.gnu.org \
--cc=_deepfire@feelingofgreen.ru \
--cc=dmantipov@yandex.ru \
--cc=skosyrev@ptsecurity.ru \
/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.