From: Drew Adams <drew.adams@oracle.com>
To: martin rudalics <rudalics@gmx.at>, emacs-devel <emacs-devel@gnu.org>
Subject: RE: Fix some tooltip related problems
Date: Thu, 11 Jan 2018 10:09:32 -0800 (PST) [thread overview]
Message-ID: <dd82bef1-216c-42be-99f9-fadc66af35d8@default> (raw)
In-Reply-To: <5A5799A5.1070305@gmx.at>
> > Can we let Lisp code (and so users too)
> > decide, here or there, which kind of tooltip to use
> > (heavyweight "Emacs" or lightweight "system")?
>
> The majority of users (namely those with a GTK build) can. Lucid and
> Motif users can't because these toolkits don't support tooltips. I
> doubt that anyone has the time to set up tooltip controls on Windows.
Dunno what that means.
1. Can users with a GTK build today use Lisp code that decides
which to use in any given (Lisp) context? How is that done
in Lisp?
2. What do you mean by "set up tooltip controls" on Windows?
Today, on Windows you can at least use faces in tooltips.
(Dunno about using images, but I'm guessing that's OK too.)
But perhaps you mean that on Windows there are _only_
"Emacs" tooltips, not "system" tooltips? From my point of
view that's not a problem - flexible beats inflexible. You
say that tooltips on Windows are "heavyweight" and "incur
an entire GC cycle", but I've never noticed any performance
problem with them - on Emacs 20 through 26.
next prev parent reply other threads:[~2018-01-11 18:09 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
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 [this message]
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
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=dd82bef1-216c-42be-99f9-fadc66af35d8@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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).