On Tue, Feb 02, 2010 at 09:24:29PM +0100, Dirk Wallenstein wrote: > XKeycodeToKeysym keeps compatibility with pre-XKB and thus only sees 2 > groups with 2 levels each. It wraps the index into the next group. > This behavior confuses the unaware user, and therefore this will add a > reference to XkbKeycodeToKeysym in the corresponding man paragraph. > > Another bug had that issue, too. #5349 > > Signed-off-by: Dirk Wallenstein <[email protected]> > --- > man/XStringToKeysym.man | 4 ++++ > 1 files changed, 4 insertions(+), 0 deletions(-) > > diff --git a/man/XStringToKeysym.man b/man/XStringToKeysym.man > index 62212db..067765b 100644 > --- a/man/XStringToKeysym.man > +++ b/man/XStringToKeysym.man > @@ -202,6 +202,10 @@ If no symbol is defined, > .ZN XKeycodeToKeysym > returns > .ZN NoSymbol . > +.ZN XKeycodeToKeysym > +predates the XKB extension. If you want to lookup a KeySym while > +using XKB you have to use > +.ZN XkbKeycodeToKeysym . > .LP > If the specified KeySym is not defined for any KeyCode, > .ZN XKeysymToKeycode > -- > 1.6.5.3
I don't insist on the phrasing of the commit message or the manual text, or me being the author. It's just that people could be easily prevented from falling into this trap. A simple 'See also' might do. Greetings, Dirk _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
