unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Item for TODO?
Date: Sat, 22 Jan 2005 13:52:33 +0200	[thread overview]
Message-ID: <01c50079$Blat.v2.4$0137bcc0@zahav.net.il> (raw)
In-Reply-To: <16882.13427.347927.500704@farnswood.snap.net.nz> (message from Nick Roberts on Sun, 23 Jan 2005 00:09:39 +1300)

> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Sun, 23 Jan 2005 00:09:39 +1300
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
> 
>  > So the only thing that's missing is to make the tty mouse support
>  > package inject help-echo events into the Emacs keyboard queue.
>  > Everything else should ``just work''.
> 
> What is a help-echo event? 

See keyboard.c, functions read_char and show_help_echo.  If the event
found (by kbd_buffer_get_event) in the keyboard queue is a list of the
special form

      (help-echo FRAME HELP WINDOW OBJECT POS)

then Emacs displays the text specified by HELP as a tooltip or an echo
area message (see the comments in keyboard.c immediately before
show_help_echo for the details).

> On an xterm, if you move the mouse around no input characters are generated
> for Emacs to read. It only knows where the mouse is when you click a
> button. In between, I don't think it knows where the mouse is.

Does this mean that the track-mouse form does not work with xt-mouse?

> How could it then display a tooltip?

If there's no way to produce input with xt-mouse, then I think
tooltips cannot be triggered by mouse movements.  You need to come up
with some other method of triggering the tooltip display.  Once you do
come up with such a method, all you need to do is make that method
produce events of the above form, and the rest will work
automagically.

  reply	other threads:[~2005-01-22 11:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21  5:58 Item for TODO? Nick Roberts
2005-01-21 15:55 ` Stefan Monnier
2005-01-21 16:42   ` John Paul Wallington
2005-01-22  8:36   ` Eli Zaretskii
2005-01-22 11:09     ` Nick Roberts
2005-01-22 11:52       ` Eli Zaretskii [this message]
2005-01-22 12:25         ` David Kastrup
2005-01-22  2:52 ` Richard Stallman
2005-01-22  7:42   ` Nick Roberts
2005-01-22 23:54     ` Richard Stallman
2005-01-23  0:35       ` Nick Roberts
2005-01-24  6:50         ` Richard Stallman
2005-01-23 10:53       ` David Kastrup

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='01c50079$Blat.v2.4$0137bcc0@zahav.net.il' \
    --to=eliz@gnu.org \
    --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 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).