Stephan Witt <[email protected]> writes:
>> However, I do not like at all the ugly code you output :)
>
> I was afraid it. :-)
> But I had to say that the implementation is not really uglier then the 
> implementation of 0x215f, e. g.
>
> 0x215f "\\LyXnumeratorone" 
> "\\newcommand*\\LyXnumeratorone{\\mbox{\\raisebox{.8ex}{1}\\kern-.175em\\raisebox{.2ex}{/}\\kern-.18em\\raisebox{-.2ex}{\\kern-.18em}}}"
>  ""
>
> But perhaps you mean the result on paper.

It was both actually. And yes, the macro above is barely acceptable...

> But I have no problem to use only plain text instead. I'll change that.
> It would become:
>
> 0x238b "{Escape}"    "" "" "" # Qt::Key_Escape
> 0x21e5 "{Tab}"       "" "" "" # Qt::Key_Tab
> 0x21e4 "{Backtab}"   "" "" "" # Qt::Key_Backtab
> 0x232b "{Backspace}" "" "" "" # Qt::Key_Backspace
> 0x2326 "{Delete}"    "" "" "" # Qt::Key_Delete
> 0x2196 "{Home}"      "" "" "" # Qt::Key_Home
> 0x2198 "{End}"       "" "" "" # Qt::Key_End
> 0x21de "{Page Up}"   "" "" "" # Qt::Key_PageUp
> 0x21df "{Page Down}" "" "" "" # Qt::Key_PageDown
> 0x21ea "{Caps Lock}" "" "" "" # Qt::Key_CapsLock
>
> or 
>
> 0x21e4 "{Shift-Backspace}"   "" "" "" # Qt::Key_Backtab
> 0x21de "{Option-Up Arrow}"   "" "" "" # Qt::Key_PageUp
> 0x21df "{Option-Down Arrow}" "" "" "" # Qt::Key_PageDown
>
> What do you like best?

I do not know. I would read the document I mentioned, that tells
precisely how each key should be named in docs.

Why are the curly braces needed, actually?

JMarc

Reply via email to