[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
master 94b6eb8: Document that :width/:height in XBM images are peculiar
From: |
Lars Ingebrigtsen |
Subject: |
master 94b6eb8: Document that :width/:height in XBM images are peculiar |
Date: |
Sun, 2 Aug 2020 13:03:33 -0400 (EDT) |
branch: master
commit 94b6eb807c8991897796fd18ccd414c7d9b9ad3b
Author: Lars Ingebrigtsen <larsi@gnus.org>
Commit: Lars Ingebrigtsen <larsi@gnus.org>
Document that :width/:height in XBM images are peculiar
* doc/lispref/display.texi (XBM Images): Note the peculiarities of
:width/:height in XBM images (bug#39735).
---
doc/lispref/display.texi | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/doc/lispref/display.texi b/doc/lispref/display.texi
index 25eabd6..d3adb62 100644
--- a/doc/lispref/display.texi
+++ b/doc/lispref/display.texi
@@ -5572,6 +5572,15 @@ The value, @var{width}, specifies the width of the
image, in pixels.
@item :height @var{height}
The value, @var{height}, specifies the height of the image, in pixels.
+Note that @code{:width} and @code{:height} can only be used if passing
+in data that doesn't specify the width and height (e.g., a string or a
+vector containing the bits of the image). @acronym{XBM} files usually
+specify this themselves, and it's an error to use these two properties
+on these files. Also note that @code{:width} and @code{:height} are
+used by most other image formats to specify what the displayed image
+is supposed to be, which usually means performing some sort of
+scaling. This isn't supported for @acronym{XBM} images.
+
@item :stride @var{stride}
The number of bool vector entries stored for each row; the smallest
multiple of 8 greater than or equal to @var{width}.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- master 94b6eb8: Document that :width/:height in XBM images are peculiar,
Lars Ingebrigtsen <=