[ Cc to Eric M. Ludlam, the speedbar maintainer, who has been very
responsive in my previous efforts to make speedbar work seamlessly
under XEmacs. ]
Andy Piper <andyp(a)parallax.co.uk> writes:
> Speedbar does this;
>
> (defcustom speedbar-frame-plist
> '(minibuffer nil width 20 border-width 0
> internal-border-width 0 unsplittable t
> default-toolbar-visible-p nil has-modeline-p nil
> menubar-visible-p nil
> ;; I don't see the particular value of these three, but...
> text-pointer-glyph [cursor-font :data "top_left_arrow"]
> nontext-pointer-glyph [cursor-font :data "top_left_arrow"]
> selection-pointer-glyph [cursor-font :data "hand2"])
>
> cursor-font isn't supported under mswindows so how do I make these X
> specific? They're not specifiers and there's no device to check when
> in custom?
OK, I've got several comments here.
1) When I split speedbar-frame-plist from speedbar-frame-alist, I
added these properties, because FSF Emacs has another method of
specifying the pointers, so I figured that this is the nicest place
to add XEmacs-specific code. Also, it seemed like a neat hack at
the time. :-)
2) I don't see any particular use in changing the default pointers for
speedbar frame, but since it was done in FSF Emacs, I figured that
it should be done in XEmacs too. So the "I don't see the value of
these three" comment is mine. If Eric agrees, we might want to
remove them altogether.
3) If you do want to keep them, they by all means do have supporting
specifiers -- just change frame-local images of text-pointer-glyph,
etc. after creating the speedbar frame.
4) I really believe :cursor and :cursor-font should be unified for
21.1, providing a platform-independent way to specify certain
things. Until then, you should implement #2 or #3 and send a patch
to Eric.
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
"Memory is like an orgasm. It's a lot better if you don't have to
fake it." -- Seymour Cray, on virtual memory