emacs/gnu.emacs
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/emacs.git synced 2026-09-10 07:46:51 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

; Minor fixes of the last change

Browse source 
* etc/NEWS: Fix last changes.

* doc/lispref/internals.texi (Module Canvas API):
* doc/lispref/display.texi (Canvas Images): Fix punctuation and
markup.
This commit is contained in:
Eli Zaretskii 2026-08-16 12:28:31 +03:00
parent d5f515e4a3
commit f4e2065697
3 changed files with 5 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/lispref/display.texi
View file

@ -7544,7 +7544,7 @@ Once a canvas image object has been created and displayed, it can be
``refreshed'' via @code{canvas-refresh}.
@defun canvas-refresh image &optional reload-data
Refresh canvas @var{image} and update it on screen. If the optional
Refresh canvas @var{image} and update it on screen. If the optional
argument @var{reload-data} is non-nil, reload the @code{:data} or
@code{file} from the image specification before redrawing the canvas.
@end defun
@ -7571,7 +7571,7 @@ When refreshing the canvas in a loop, we must explicitly call @code{redisplay}:
@end example
But, if we are refreshing the canvas via a timer or a command, @code{redisplay}
is implicitly called after the timer or command. The following example updates
is implicitly called after the timer or command. The following example updates
the above canvas in a timer ~30 times per second:
@example

4
doc/lispref/internals.texi
View file

@ -2035,7 +2035,7 @@ with dynamic modules:
@anchor{canvas_data}
@deftypefn Function uint32_t *canvas_data (emacs_env *@var{env}, emacs_value @var{canvas})
The function gives access to the pixel buffer of @var{canvas}. The
pixel buffer is in row-major order with a size @var{width} * @var{height}.
pixel buffer is in row-major order with a size @code{@var{width}x@var{height}}.
The pixel format is ARGB32 on all platforms. Return @code{NULL} in case
of error.
@end deftypefn
@ -2061,7 +2061,7 @@ env->funcall(env, env->intern(env, "canvas-refresh"), 2,
Note that @code{canvas-refresh} has an optional boolean argument to
reload the @code{:data} vector or string from the canvas image
specification. When called from dynamic modules, the argument should
usually be @code{nil}.
usually be @code{Qnil}.
Thus, one can simply define a module function that takes as an argument
a canvas image object, following the specification as laid down in

4
etc/NEWS
View file

@ -33,8 +33,6 @@ systems.
* Changes in Emacs 32.1
+++
---
** Emacs no longer kills child processes after EPIPE.
Previously, Emacs would immediately kill a child process and set its
@ -316,7 +314,7 @@ older '(HIGH LOW USEC PSEC)' form.
+++
** Support for canvas image objects.
Canvas images support efficient updating and refreshing. An image
specifier with ':type canvas' creates a canvas image. The canvas has an
specifier with type 'canvas' creates a canvas image. The canvas has an
associated writable pixel buffer. The dynamic module function 'canvas_data'
provides access to the pixel buffer. After changing the ':data' vector or
writing to the pixel buffer a call to 'canvas-refresh' redraws the canvas