>>>>> "John" == John Spray <[EMAIL PROTECTED]> writes:
John> On Tue, 2004-09-28 at 16:24, John Spray wrote: >> > While I do not have anything useful to say about the errors, I'd >> like > to point you to GLyXKeySym::print, which is the right hook >> for > generating a correct string corresponding to a given keysym. >> Currently > it points to kb_keymap::printKeySym, which gives the >> C-S-n, but > you can rewrite it to your liking as is done in >> QLyXKeySym::print. >> >> Thanks, it's much better for me to do it that way. Revised patch >> attached. John> Spoke too soon: it looks like that function is also used for John> describing accelerators in the minibuffer/statusbar, so it John> really needs to be human readable. Thus, the original version John> was better. And what would be the right gtkmm method to get a nice human-readable version? The part of the code that handles this shortcuts is designed to work with xforms and Qt. If changes are needed to get gtk to work, I am willing to do them. What I think we should do is expose properly the key sequences to the frontends. Currently, this does not work very well, because kb_sequence is a rather opaque object. JMarc
