all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Fix some tooltip related problems
Date: Thu, 11 Jan 2018 11:56:39 +0100	[thread overview]
Message-ID: <5A5742E7.3070303@gmx.at> (raw)
In-Reply-To: <475d480b-3885-4779-ae46-09cf7fbbcee7@default>

 > I thought that Emacs tooltips were Emacs frames.  What
 > prevents Emacs from doing what it wants in such a frame?
 > This works for me, for example:
 >
 > (x-show-tip (propertize "abc" 'face '(:foreground "gray")))
 >
 > What's different here from what you are talking about?
 >
 > OK, I'm using MS Windows.  But does this not work also
 > on GNU/Linux and Mac?
 >
 > And if that doesn't work on such platforms, can't we use
 > a ("normal") Emacs frame where such things do work?  Just
 > what is it that makes it impossible for Emacs to dim the
 > text in a tooltip?  Sorry, but this is not clear to me.

System tooltips are lightweight objects with restricted abilities.
They have uniform appearance and the single tooltip window is usually
shared among all running programs and the operating system.

Emacs tooltips are merely an emulation of system tooltips.  Most
restrictions of system tooltips have been retrofit artificially, like
uniform faces which are built into `tooltip-show' (but can be avoided
by using `x-show-tip' as you mention above) or the fact that only one
tooltip can be present at any time.

The great disadvantage of Emacs tooltips is that they are heavyweight
precisely due to their versatility.  Showing an Emacs tooltip here on
Windows with -Q incurs an entire GC cycle.  Also, there are some minor
annoyances like the one that showing Emacs tooltips for menu items
depends on the presence of a blinking cursor.

martin



  parent reply	other threads:[~2018-01-11 10:56 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08  9:53 Fix some tooltip related problems martin rudalics
2018-01-08 14:41 ` Drew Adams
2018-01-08 18:19   ` martin rudalics
2018-01-08 18:50     ` Drew Adams
2018-01-09  9:42       ` martin rudalics
2018-01-09 15:08         ` Drew Adams
2018-01-10 10:20           ` martin rudalics
2018-01-10 15:55             ` Drew Adams
2018-01-10 19:17               ` Alan Third
2018-01-10 21:02                 ` Drew Adams
2018-01-10 23:04                   ` Alan Third
2018-01-10 23:26                     ` Drew Adams
2018-01-11  3:39                   ` Eli Zaretskii
2018-01-11  7:03                 ` Yuri Khan
2018-01-11 14:32                   ` Drew Adams
2018-01-11 10:56               ` martin rudalics [this message]
2018-01-11 14:42                 ` Drew Adams
2018-01-11 17:06                   ` martin rudalics
2018-01-11 17:19                     ` Robert Pluim
2018-01-11 17:59                       ` Eli Zaretskii
2018-01-11 18:20                         ` martin rudalics
2018-01-11 23:33                         ` Daniele Nicolodi
2018-01-12  8:38                           ` Eli Zaretskii
2018-01-12  8:40                         ` Robert Pluim
2018-01-12  9:55                           ` Eli Zaretskii
2018-01-12 13:57                             ` Robert Pluim
2018-01-12 14:15                               ` Philipp Stephani
2018-01-11 19:54                       ` Richard Stallman
2018-01-11 23:26                       ` Stefan Monnier
2018-01-12  8:48                         ` Robert Pluim
2018-01-11 18:09                     ` Drew Adams
2018-01-11 18:54                       ` martin rudalics
2018-01-11 19:50                         ` Drew Adams
2018-01-12  8:47                           ` martin rudalics
2018-01-12 16:43                             ` Drew Adams
2018-01-08 18:47 ` Eli Zaretskii
2018-01-08 19:06   ` martin rudalics
2018-01-08 19:22     ` Eli Zaretskii
2018-01-09  9:42       ` martin rudalics
2018-01-19 18:54 ` martin rudalics

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=5A5742E7.3070303@gmx.at \
    --to=rudalics@gmx.at \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    /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.