[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs-devel Digest, Vol 131, Issue 82

From: David Requena Zabala
Subject: Re: Emacs-devel Digest, Vol 131, Issue 82
Date: Tue, 20 Jan 2015 17:35:05 +0100

Many, many, thanks!
Now lets see if my skills are up to ?emacs level :-)


Note: this e-mail composed while on mobility, please bear with any typing 

  Original Message
From: Eli Zaretskii
Sent: martes, 20 de enero de 2015 17:28
To: David Requena Zabala
Reply To: Eli Zaretskii
Cc: address@hidden
Subject: Re: Emacs-devel Digest, Vol 131, Issue 82

> From: David Requena Zabala <address@hidden>
> Date: Tue, 20 Jan 2015 10:23:37 +0100
> At any rate, if someone was to implement an hypothetical
> '--without-w32-toolkit-scroll-bars', would it take entering much into the 
> elisp
> realm?

No, it shouldn't touch the Lisp level at all.  The implementation of
the scroll bars is entirely on the C level.

> Probably having different kinds of sc means some form of common scroll bar api
> exists for sc implementation code to use and/or plug in. I mean, kind of how
> the w32_wnd_proc callback handles the WM_EMACS_CREATESCROLLBAR message by
> calling w32_createscrollbar. Is this the case? Is it described somewhere?

See w32term.c:w32_set_vertical_scroll_bar for the Windows
implementation and xterm.c:XTset_vertical_scroll_bar for the X
implementation.  The guts are in x_scroll_bar_create in both cases,
but the API you were asking about is defined by the former two
functions, which implement the hook called by Emacs when it wants to
display the scroll bar.  How this maps into the windowing system is
entirely hidden from the higher levels; on Windows this sends a
message to the GUI thread, which calls the corresponding Windows API.

 David Requena Zabala
 Comunicaciones Internacional

  Tel: 985 732 273
 C/ Dinamarca, nº19, 2º, Pol. Ind. Espíritu Santo
 33010 Oviedo Asturias

Visite nuestra web de venta http://www.gamusado.com/
P Tenga en cuenta las consecuencias para el medio ambiente antes de imprimir 
este mensaje.
Este mensaje contiene información de carácter privado y CONFIDENCIAL y se 
dirige exclusivamente a su destinatario. Si usted no es el destinatario al que 
se dirige, le rogamos que nos lo comunique por teléfono o correo electrónico, 
proceda a su destrucción y no debe leerlo, copiarlo, utilizarlo ni difundirlo.
This message contains privileged and CONFIDENTIAL information and is intended 
exclusively for its addressee. If you are not the intended recipient, please 
telephone or email the sender, delete it and do not read, copy, use or disclose 
it. (A)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]