"Eric M. Ludlam" <zappo(a)ultranet.com> writes:
>>> Hrvoje Niksic <hniksic(a)srce.hr> seems to think
that:
>"Eric M. Ludlam" <zappo(a)ultranet.com> writes:
>
>No, your call to decide whether speedbar should specify this stuff
>explicitly in its frames. I think it's not really needed.
>
>I think it is not needed.
I'm perfectly happy to remove the cursor bindings for those
situations where they are non functional. However, my opinion for
changing the default cursors (when available) is that speedbar is
not an editor. Well, technically it's an editor, but it's trying to
represent non-editor things. Its a mutation of a tree widget or
list. As such, a text I beam is not applicable because there is no
text to "edit".
I can follow your reasoning, but shouldn't the same apply to W3 mode,
Customize and even Gnus and VM? All of them represent "non-editor"
things in very much the same way, so your pointer changes look
gratuitous to me.
Anyway, if you insist that the speedbar pointer shapes must differ
from others, it should be implemented for all window systems. All you
need to do is remove the properties from the plist and set up the
frame-specific instantiators at the same place where you create the
Speedbar frame. Something like:
(cond ((eq (console-type) 'x)
(set-glyph-image text-pointer-glyph [cursor-font ...]
speedbar-frame)
...)
((eq (console-type) 'mswindows)
(set-glyph-image text-pointer-glyph [resource ...]
speedbar-frame)
...))
In the greater scheme of things it makes little difference, but
every little bit helps. :)
I would say the same thing, but for the contrary.
Anyway, I'll make the ms windows change for the next version
based
on Andy's earlier technical information.
Please don't. I'd like XEmacs to behave the same under all window
systems, as far as possible.
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
main(){printf(&unix["\021%six\012\0"],(unix)["have"]+"fun"-0x60);}