unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 20540@debbugs.gnu.org
Subject: bug#20540: 25.0.50; Document tooltip woes, including `help-echo'
Date: Sat, 9 May 2015 16:27:05 -0700 (PDT)	[thread overview]
Message-ID: <795eb88f-e9e7-4728-82d8-32d0caea52fb@default> (raw)

1. If you create a tooltip using, say, `x-show-tip', you can control the
font, text color and size, background color, etc.  Well, only some frame
parameters seem to have any effect, when passed in argument PARMS.  Just
which parameters can or cannot be used for PARMS should be documented.

2. The word `tooltip' is hardly mentioned in the doc.  Another doc fix
would be to document `tooltip-mode' properly in the Elisp manual, saying
which frame parameters you can use for `tooltip-frame-parameters', etc.

3. A related bug in `tooltip.el' is that the defcustom for
`tooltip-frame-parameters' has no :type.  Impossible for a user to
customize the value properly using Customize.  And no help about which
parameters can be used effectively (see #2, above).

4. `help-echo': No doc saying whether the string can be propertized, and
if so, which properties have any effect.  Although `x-show-tip' seems to
let you change the char size, color, background color, etc., and you can
use property `display' with `help-echo', apparently you cannot change
the face attributes of the `help-echo' string so that the appearance
changes.  This is quite a limitation, AFAICT.

All of this kind of thing should be documented: what you can and cannot
do - which parameters have an effect.  You can make `help-echo' show an
image instead of text, but you cannot simply change the text appearance
of a `help-echo' string?  How are users supposed to guess what is
possible?  Should be documented.



In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
 of 2014-10-20 on LEG570
Bzr revision: 118168 rgm@gnu.org-20141020195941-icp42t8ttcnud09g
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --enable-checking=yes,glyphs CPPFLAGS=-DGLYPH_DEBUG=1'





             reply	other threads:[~2015-05-09 23:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-09 23:27 Drew Adams [this message]
2015-05-10  2:48 ` bug#20540: 25.0.50; Document tooltip woes, including `help-echo' Eli Zaretskii
2015-05-10 14:38 ` Eli Zaretskii
2021-06-22 14:42 ` Lars Ingebrigtsen
     [not found] <<795eb88f-e9e7-4728-82d8-32d0caea52fb@default>
     [not found] ` <<83d229no4x.fsf@gnu.org>
2015-05-10 14:36   ` Drew Adams
2015-05-10 15:26     ` Eli Zaretskii
     [not found] ` <<83bnhso5u8.fsf@gnu.org>
2015-05-10 16:11   ` Drew Adams

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=795eb88f-e9e7-4728-82d8-32d0caea52fb@default \
    --to=drew.adams@oracle.com \
    --cc=20540@debbugs.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 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).