On Fri, 18 Jul 2003, Angus Leeming wrote: [Inset to display key binding dynamically based on command name]
> I even coded it up (2/3 years ago?), but for reasons I didn't quite > understand it was dropped. (I was young then and lacked knowledge.) If I remember correctly, I suggested this a long time ago, but Jean-Marc did not like it, because then you could not really use a printed version as a reference to LyX. Personally, I think that does not matter, but maybe a combination of the branch business and an automatic inset could clear the waters and satisfy all: - The inset would get a command name as input - You can configure it to display either the key binding, the menu position, or the name, tooltip, or whatever relevant information we have in the code. Alternatively, each of these should have their own inset. - Based on the branching infra-structure, you can choose whether to export the CUA key binding, the Emacs key binding, the Qt front-end menu position, the XForms menu position, or whatever. Such an inset seems to me to be much more maintainable than hard-coded key bindings and positions in the documentation. Regards, Asger
