-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 04 May 2003 00:17, Chris Osicki wrote:
> 
> Hi,
> 
> I noticed a strange behavior of Kword in regard to how it interprets 
> keyboard. It looks like its view of the keyboard differs from the
> X-server's one.
> I use on my PC a Sun keyboard which has "additional" function keys on
> the left hand site. I can "xmodmap" them and I use them under X or KDE
> (assigned some of them to functions in Sawfish or applications like 
> Emacs). 
> It looks like Kword has its own view of what a keycode should
> translate to.
I guess all Qt/KDE applications have that view though.

> In other words, it looks like it takes keycodes and does the
> translation itself. 
I don't think so, but I could be wrong.

> So, X-server translates keycode 125 to keysym
> 0x1005ff72, SunCopy, for Kword it is an undefined keystroke.
Well, it obviously is :)
Strangely enough, the code I got from Qt said
    case Key_F16: // Copy key on Sun keyboards
    case Key_F18:  // Paste key on Sun keyboards
    case Key_F20:  // Cut key on Sun keyboards
This looks quite strange though, it could easily conflict with other custom definitions
for function keys.
Can you uncomment the line at koffice/lib/kotext/kotextview.cc:280, adding << " key=" << e->key()
to it, to see exactly what Qt receives?
There's no Key_SunCopy though, that's for sure...

Also, you could try "Configure shortcuts" and see what it says when
you press the SunCopy key.

- -- 
David Faure -- faure@kde.org, dfaure@klaralvdalens-datakonsult.se
Qt/KDE/KOffice developer
Klarälvdalens Datakonsult AB, Platform-independent software solutions
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+tMvU72KcVAmwbhARAj3iAJ9uaZO3ipdBfIJ7TTniLb2Y3Xc+fACdHnEb
jZtNGcVZ+AgZsYKOH8QOyWQ=
=THB9
-----END PGP SIGNATURE-----

____________________________________
koffice mailing list
koffice@mail.kde.org
To unsubscribe please visit:
http://mail.kde.org/mailman/listinfo/koffice