On Sun, Dec 23, 2012 at 7:24 PM, Stephen J. Turnbull <stephen(a)xemacs.org>wrote:
Is there a use case for the :active keyword in submenus?
Well, we're making a different menu interface to the register
functionality.
This makes submenus for each function (like "Copy to
Register" or " Insert from Register) with entries for a bunch of different
registers. Those use suffixes, etc. to preview the values for easy
insertion/copying. From a tree perspective:
|+Copy to Register
|| a (a contents)
|| b (b contents)
|+Insert from Register
|| a (a contents)
|| b (b contents)
etc.
We were looking at using :active to disable the submenus for functions that
need an active region, whenever the region isn't active. We can always use
:included, but it seems more natural to have an entry there even if it's
impossible to use.
Thanks for the patches! I've got a few more old patches I want to
clear out of my workspace, and then I'll try to take a bite out
of the
backlog of user patches.
You're welcome. We just happen to be poking in this section of the code
right now. There was one thing I was wondering about when reading through
the menubar.el. There's a lot of special-casing to handle the fact that the
top-level menu doesn't have a leading string. Is there a good reason for
this, other than just history? Ben and I were thinking about rehashing it
to work with a leading string (probably just "") if that's something you
guys would be interested in looking at. On the other hand, I don't know if
there might be a lot of packages and whatnot that directly access the menu
that such a change might break.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta