From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: The display margin
Date: 27 Nov 2003 23:30:11 +0100 [thread overview]
Message-ID: <x5oeuxwiks.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3oeuxpfyj.fsf@kfs-l.imdomain.dk>
storm@cua.dk (Kim F. Storm) writes:
> David Kastrup <dak@gnu.org> writes:
>
> > The click information for GNU Emacs is quite insufficient, anyway.
> > XEmacs, as far as I can remember, can tell from an event what object
> > has been clicked on and what pixel relative to the object's origin
> > has been hit.
>
> I have just added this information to mouse clicks and two functions to
> access it:
>
> Function `posn-object' returns the object clicked on, either an image
> or a cons (string . pos), or nil if there is nothing special at the
> place where you click the mouse (use posn-point to look at that).
>
> Function `posn-object-x-y' return a cons (dx . dy) which is the pixel
> coordinates relative to the top left corner of the object (image or
> character) that you click on.
>
> In addition, the mouse cursor now changes to an arrow (rather than the
> text mouse cursor) when it hoovers above an image.
Rationale for that? Just interested. Maybe this should rather depend
on an appropriate image property?
> Finally, when you use a block cursor, images are no longer shown in
> "negative" when your window cursor is a filled block cursor (only
> the border of the image is highlighted now). So clicking on an
> image no longer makes it "unreadable"...
Oh great. That means that all the complicated image border creation
stuff within preview-latex becomes unnecessary, and we'll have to
check for this functionality conditionally. Any good idea for a test
for whether the previous terror blinking or the new border blinking is
used on images?
> > I digress. Anyway, I want more information from clicks. At the
> > very least, the object they appeared on.
>
> What more do you want ?
Well, further preview-latex usability problems are that Emacs often
goes ballistic when large height images are concerned, particularly
larger than window size images. Scrolling those to a particular
viewing position is pretty much impossible, scrollbar interaction is
nonworkable, and scroll-wheel stuff is pretty much unpredictable as
well (there have been Emacs versions where wheel-use could lead to
lockup with large images, I am not sure whether this is currently the
case).
When using XEmacs on such images, repeated use of Pagedown scrolled
larger-than-window images through at a pace of about one normal line
height per keypress. While this was far from scrolling a window worth
of material, at least the scrolling made some progress and one had a
possibility to see all parts of such an image.
In contrast, IIRC, Emacs does not even touch the window-vscroll value
(which would move by a fraction of the image) unless at the very end
of buffer.
One possibility to see the effect it to use
C-h i d m Emacs RET C-x 2
and drag the mode line of the upper window such that the "Emacs"
headline is only partially visible.
Repeated presses of C-v will then stop on the headline and not make
any more progress.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2003-11-27 22:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-25 16:22 The display margin Nick Roberts
2003-05-25 16:36 ` Stefan Monnier
2003-05-26 23:42 ` Nick Roberts
2003-11-23 2:08 ` Kim F. Storm
2003-11-23 22:53 ` Nick Roberts
2003-11-23 23:12 ` David Kastrup
2003-11-24 9:52 ` Kim F. Storm
2003-11-24 15:33 ` Kim F. Storm
2003-11-27 23:08 ` Kim F. Storm
2003-11-27 22:30 ` David Kastrup [this message]
2003-11-27 23:17 ` Stefan Monnier
2003-11-28 11:09 ` Kim F. Storm
2003-11-28 10:53 ` David Kastrup
2003-11-28 14:23 ` Thien-Thi Nguyen
2003-11-28 16:02 ` David Kastrup
2003-11-28 17:01 ` Thien-Thi Nguyen
2003-11-29 3:15 ` Kim F. Storm
2003-11-29 11:37 ` David Kastrup
2003-12-01 10:15 ` Kim F. Storm
2003-12-01 13:08 ` David Kastrup
2003-12-28 1:43 ` Kim F. Storm
2003-12-29 11:54 ` Richard Stallman
2003-11-24 0:09 ` Kim F. Storm
2003-11-25 21:11 ` Nick Roberts
2003-11-25 22:42 ` Kim F. Storm
-- strict thread matches above, loose matches on Subject: below --
2003-11-28 12:47 David PONCE
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=x5oeuxwiks.fsf@lola.goethe.zz \
--to=dak@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).