From koffice  Tue May 06 20:04:40 2003
From: David Faure <dfaure () klaralvdalens-datakonsult ! se>
Date: Tue, 06 May 2003 20:04:40 +0000
To: koffice
Subject: Re: Kword and function keys
X-MARC-Message: https://marc.info/?l=koffice&m=105225230511208

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

On Tuesday 06 May 2003 21:23, Chris Osicki wrote:
> Well, I don't know what to say. I "xmodmap" those function keys giving
> them names like SunCopy, SunCut etc. Those keysyms (SunCopy, SunCut)
> are not my invention, they are predefined
I know.

> No I see there is another keyboard definition in:
> /usr/X11R6/lib/X11/xkb/symbols/sun/us
> where SunCopy and F16 are used.
> I see some applications refering to my SunCopy key as F16 (even if I
> xmodmape'ed it to SunCopy and xev shows SunCopy) and it works.
Qt apps or other apps?

> > > 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.
> 
> On which keyboards? ;-) 

Any keyboard with extra key, like those multimedia keyboards. It's common to
map those as F13 to F20.

- -- 
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.2.1 (GNU/Linux)

iD8DBQE+uBVY72KcVAmwbhARAgtVAJ450tQ5l9lWY2azX+fUW+cVphgfagCgkg+I
pjnhPGLx2ZgD7YF2D9LVfMw=
=aZrs
-----END PGP SIGNATURE-----

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