From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: 20677@debbugs.gnu.org
Subject: bug#20677: tooltips generate garbage
Date: Tue, 02 Jun 2015 05:33:07 +0300 [thread overview]
Message-ID: <83oakysuu4.fsf@gnu.org> (raw)
In-Reply-To: <556CD4EB.8080602@alice.it>
> Date: Mon, 01 Jun 2015 23:55:55 +0200
> From: Angelo Graziosi <angelo.graziosi@alice.it>
> CC: 20677@debbugs.gnu.org, jan.h.d@swipnet.se
>
> Il 01/06/2015 18:19, Eli Zaretskii ha scritto:
> >> Date: Mon, 01 Jun 2015 17:58:36 +0200
> >> From: Angelo Graziosi <angelo.graziosi@alice.it>
> >> CC: 20677@debbugs.gnu.org, jan.h.d@swipnet.se
> >>
> >> Hmm... given the issue and looking at the changes, this caught my attention:
> >>
> >> --- a/src/gtkutil.c
> >> +++ b/src/gtkutil.c
> >> @@ -3824,8 +3824,7 @@ xg_update_scrollbar_pos (struct frame *f,
> >> above. */
> >> oldw += (scale - 1) * oldw;
> >> oldx -= (scale - 1) * oldw;
> >> - x_clear_area (FRAME_X_DISPLAY (f), FRAME_X_WINDOW (f),
> >> - oldx, oldy, oldw, oldh);
> >> + x_clear_area (f, oldx, oldy, oldw, oldh);
> >>
> >> maybe, on linux+X Emacs needs something like this
> >>
> >> # if def(...X11..)
> >> [...]
> >> x_clear_area (FRAME_X_DISPLAY (f), FRAME_X_WINDOW (f)...
> >> #else
> >> x_clear_area (f, oldx, oldy, oldw, oldh)...
> >> #endif
> >
> > No, the calling sequence of x_clear_area has changed, so that change
> > was correct, I think. Are you saying that reverting it makes tooltips
> > work again?
>
> Really I didn't tested that.. Eventually, I will test that over the next
> few days..
Can you show a screenshot of the bad tooltip display?
next prev parent reply other threads:[~2015-06-02 2:33 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 21:40 bug#20677: tooltips generate garbage Angelo Graziosi
2015-05-28 2:43 ` Eli Zaretskii
2015-06-01 11:46 ` Angelo Graziosi
2015-06-01 14:36 ` Eli Zaretskii
2015-06-01 15:58 ` Angelo Graziosi
2015-06-01 16:19 ` Eli Zaretskii
2015-06-01 21:55 ` Angelo Graziosi
2015-06-02 2:33 ` Eli Zaretskii [this message]
2015-06-02 9:23 ` Angelo Graziosi
2015-06-02 9:35 ` Angelo Graziosi
2015-06-02 14:57 ` Eli Zaretskii
2015-06-02 15:31 ` Michael Heerdegen
2015-06-02 15:39 ` Michael Heerdegen
2015-06-02 15:54 ` Michael Heerdegen
2015-06-02 16:16 ` Eli Zaretskii
2015-06-02 16:33 ` Michael Heerdegen
2015-06-02 19:08 ` Eli Zaretskii
2015-06-03 7:01 ` YAMAMOTO Mitsuharu
2015-06-03 13:51 ` Angelo Graziosi
2015-06-03 16:10 ` Michael Heerdegen
2015-06-03 16:43 ` Eli Zaretskii
2015-06-03 17:02 ` Michael Heerdegen
2015-06-03 19:14 ` Eli Zaretskii
2015-06-04 5:25 ` YAMAMOTO Mitsuharu
2015-06-04 15:37 ` Eli Zaretskii
2015-06-05 0:50 ` YAMAMOTO Mitsuharu
2015-06-05 7:04 ` Eli Zaretskii
2015-06-02 17:06 ` Michael Heerdegen
2015-06-02 17:08 ` Wolfgang Jenkner
2015-06-02 16:02 ` Eli Zaretskii
2015-06-02 16:14 ` Michael Heerdegen
2015-06-02 17:04 ` Angelo Graziosi
2015-06-02 18:56 ` Eli Zaretskii
2015-06-02 0:31 ` Wolfgang Jenkner
2015-06-02 9:21 ` Angelo Graziosi
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=83oakysuu4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20677@debbugs.gnu.org \
--cc=angelo.graziosi@alice.it \
/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).