summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorLars Ingebrigtsen <larsi@gnus.org>2022-08-25 16:38:14 +0200
committerLars Ingebrigtsen <larsi@gnus.org>2022-08-25 17:03:11 +0200
commitec4f976e8e1c072d6d6e05d77009e79da9efe885 (patch)
tree9764d8ed05440fda82e8072b1a0909c8b25f6596 /doc
parent514372722a5d611b37c818f66646497268605ac2 (diff)
downloademacs-ec4f976e8e1c072d6d6e05d77009e79da9efe885.tar.gz
Document how :map and :scale interacts in image maps
* doc/lispref/display.texi (Image Descriptors): Mention problems with scaling (bug#50487).
Diffstat (limited to 'doc')
-rw-r--r--doc/lispref/display.texi8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/lispref/display.texi b/doc/lispref/display.texi
index d336cda6743..fde7274d591 100644
--- a/doc/lispref/display.texi
+++ b/doc/lispref/display.texi
@@ -5886,6 +5886,14 @@ When you click the mouse when the mouse pointer is over a hot-spot, an
event is composed by combining the @var{id} of the hot-spot with the
mouse event; for instance, @code{[area4 mouse-1]} if the hot-spot's
@var{id} is @code{area4}.
+
+Note that the map's coordinates should reflect the displayed image
+after all transforms have been done (rotation, scaling and so on), and
+also note that Emacs (by default) performs auto-scaling of images, so
+to make things match up, you should either specify @code{:scale 1.0}
+when creating the image, or use the result of
+@code{image-compute-scaling-factor} to compute the elements of the
+map.
@end table
@defun image-mask-p spec &optional frame