unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ken Raeburn <raeburn@permabit.com>
Cc: 21473@debbugs.gnu.org
Subject: bug#21473: 24.5; very slow tooltip display to sort-of-slow remote display
Date: Tue, 06 Oct 2015 17:46:34 +0300	[thread overview]
Message-ID: <83io6kxdf9.fsf@gnu.org> (raw)
In-Reply-To: <B047C786-6682-48AC-8E88-7E632A9A2203@permabit.com>

> From: Ken Raeburn <raeburn@permabit.com>
> Date: Tue, 6 Oct 2015 05:30:42 -0400
> Cc: 21473@debbugs.gnu.org
> 
> It looks like I was mistaken. It appears that it was using the arrow only because that’s the default pointer shape for the X root window. According to some of the X docs I was reading, if the “cursor” (pointer shape) is never defined for a window, then the window uses the value from the parent window.
> 
> If I change the root window’s default pointer shape, then when the mouse is in the tooltip window it also uses that shape. I doubt that’s what we want; one of the shapes used by Emacs would be better, even if we only allow one to be used for that frame. Then again, if the window is supposed to go away quickly, maybe we don’t care at all? On a slow, remote link, there can be enough lag for the pointer to be visible in the tooltip window for a good half second at least.
> 
> The odd part: It appears that it’s already broken, even with the call to x_set_mouse_color being applied to the tooltip frame. I’m still getting whatever odd cursor shape I installed for the root window. This is with the Xquartz server on OS X; I’ll try later with the X.org server.

I suggest to make that call conditional on a user variable, by
default off.  Most users, certainly on fast networks, will never see
that pointer anyway.

WDYT?





  reply	other threads:[~2015-10-06 14:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14  8:13 bug#21473: 24.5; very slow tooltip display to sort-of-slow remote display Ken Raeburn
2015-09-15 14:32 ` Eli Zaretskii
2015-09-15 22:03   ` Ken Raeburn
2015-09-26  7:03 ` Eli Zaretskii
2015-09-27 10:35   ` Ken Raeburn
2015-09-27 10:38     ` Eli Zaretskii
2015-09-27 13:29       ` Ken Raeburn
2015-09-29 20:15         ` Ken Raeburn
2015-09-30  7:23         ` Eli Zaretskii
2015-10-01 10:01           ` Ken Raeburn
2015-10-01 16:51             ` Ken Raeburn
2015-10-04  9:45             ` Eli Zaretskii
2015-10-04 18:02               ` Ken Raeburn
2015-10-04 19:40                 ` Eli Zaretskii
2015-10-05  5:38                   ` Ken Raeburn
2015-10-05  6:25                     ` Eli Zaretskii
2015-10-06  2:15                       ` Ken Raeburn
2015-10-06  2:44                         ` Eli Zaretskii
2015-10-06  9:30                           ` Ken Raeburn
2015-10-06 14:46                             ` Eli Zaretskii [this message]
2015-10-07  6:09                               ` Ken Raeburn
2015-10-07 15:31                                 ` Eli Zaretskii
2015-10-08  6:04                                   ` Ken Raeburn
2015-10-08  8:12                                     ` Ken Raeburn
2021-09-19 22:29                                       ` Stefan Kangas
2022-04-24 13:19                                         ` Lars Ingebrigtsen
2022-04-25  2:09                                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23  8:02                                         ` 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

  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=83io6kxdf9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21473@debbugs.gnu.org \
    --cc=raeburn@permabit.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).