From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: The display margin Date: 29 Nov 2003 04:15:27 +0100 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <16080.60869.212521.952911@nick.uklinux.net> <200305251636.h4PGa1ll021935@rum.cs.yale.edu> <16082.42589.935105.932019@nick.uklinux.net> <16321.14941.117864.117597@nick.uklinux.net> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1070072341 9745 80.91.224.253 (29 Nov 2003 02:19:01 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 29 Nov 2003 02:19:01 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sat Nov 29 03:18:58 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1APuhG-0003rS-00 for ; Sat, 29 Nov 2003 03:18:58 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1APuhG-0005fz-00 for ; Sat, 29 Nov 2003 03:18:58 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1APvd5-0001a1-5w for emacs-devel@quimby.gnus.org; Fri, 28 Nov 2003 22:18:43 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1APvcr-0001Zw-HB for emacs-devel@gnu.org; Fri, 28 Nov 2003 22:18:29 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1APvcL-0001Yi-KD for emacs-devel@gnu.org; Fri, 28 Nov 2003 22:18:28 -0500 Original-Received: from [193.162.153.3] (helo=pfepb.post.tele.dk) by monty-python.gnu.org with esmtp (Exim 4.24) id 1APvbp-0001XL-LL; Fri, 28 Nov 2003 22:17:25 -0500 Original-Received: from kfs-l.imdomain.dk.cua.dk (0x503e2644.bynxx3.adsl-dhcp.tele.dk [80.62.38.68]) by pfepb.post.tele.dk (Postfix) with SMTP id B53515EE15A; Sat, 29 Nov 2003 03:15:59 +0100 (CET) Original-To: David Kastrup In-Reply-To: Original-Lines: 81 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:18200 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18200 David Kastrup writes: > storm@cua.dk (Kim F. Storm) writes: > > > David Kastrup writes: > > > > > > 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? > > > > That would be an improvement, yes. Will see what I can do. > > > > The rationale is that the "active point" of text cursor (the > > vertical bar) is somewhere in the middle of the vertical line, > > i.e. it's no good as a pointer if you want to have precise clicks on > > an image. > > > > But of course, if that image is showing text, a text cursor may > > still make sense... > > In general, a change of cursor is an indicator that the behavior of > clicking will change. Since different cursors might indicate > different behaviors, it certainly makes sense to have this as a > separate property. I will add both a generic 'pointer' text property, and a specific image :pointer property. Maybe also an image :keymap property, but that will require more work, so I will have to investigate further before doing so. > Now there is one situation when one _does_ have a > change-of-behavior-on-click, and that is when we have a local keymap > on the image, in particular one with mouse clicks in it. But this is > not really fundamentally different from textual buttons (like the > widgets used in customization buffers). So _if_ we get a default > cursor change, I think it should be orthogonal to the image issue and > rather depend on keymaps. I think an explicit pointer property is better; then you can always get the exact behaviour you want (who says that just because there is a local keymap as some position, that keymap has any mouse-specific bindings)? > > > > > 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"... > > > > > Is this good or bad? > > It would have been even better if it had been done previously. That's life... > > > or newer would do... But if you want something which really narrows > > down when this was introduced, (fboundp 'posn-object-x-y) will do. > > This has such an _indirect_ flavor to it. Let's hope that nobody > does a branch having one but not the other feature. Sure. Maybe (boundp 'void-text-area-pointer) will be better as it's in the C code [will be when my current fixes are committed in a few days]. > > I was just asking in the context of "required information in mouse > > click events". Your answer seems to be "nothing further". > > Actually, given that we now have a pixel-accurate position within the > object (maybe this is generalizable in some manner also for text?), it > would be nice having a way of knowing the pixel-accurate size of a > displayed object in the first place so that one can calculate the > relative position in the image easily, too. I'll look into adding this info as well ... at least for images. -- Kim F. Storm http://www.cua.dk