wmperry(a)aventail.com (William M. Perry) writes:
Hrvoje Niksic <hniksic(a)srce.hr> writes:
> wmperry(a)aventail.com (William M. Perry) writes:
>
> > Why not make button1 do what you want there?
>
> Context-sensitive menus have always been activated by button3, not
> button1 or button2. Widgets like `State' look like a context-sensitive
> menu to me.
This isn't really context-sensitive though. That is _all_ the state
button is meant to do.
Yes, but when you click on a particular State button, you get the menu
pertaining to that button, not to all buttons. It's
context-sensitive.
The context-sensitive menus should be offering _additional_
functionality than the widget's main purpose.
I agree. But then again, I've always thought that the State widget's
main purpose was very ugly in the UI sense. I haven't seen anything
else in Emacs pop up a menu when button2 is pressed on it.
> > You wouldn't be able to get the standard context
sensitive menus
> > in a GNUS article buffer if you just happened to have a
> > buttonized/widgetized chunk of text under your mouse.
>
> Gnus article buffers don't have context-sensitive menus. If you
> are over a button/widget, button3 should present you a
> widget-specific menu.
_mode_ sensitive menus, they do. And the mode you are in, to me, is
part of the context. So they are context sensitive.
Bah. That's not "context-sensitive". Call it buffer-local or
mode-local, but not context-sensitive.
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
"A Real Programmer's code can awe with its fiendish brilliance, even
as its crockishness appalls."