Ah, didn't know about that. I'll fix my wayland backend to handle that.
On 28/10/2013 3:23 pm, "Rainer Hochecker" <notifications@github.com> wrote:

> In xbmc/windowing/WinEventsX11.cpp:
>
> > +
> > +XBMCKey CWinEventsX11Imp::LookupXbmcKeySym(KeySym keysym)
> > +{
> > +  // try direct mapping first
> > +  std::map<uint32_t, uint32_t>::iterator it;
> > +  it = WinEvents->m_symLookupTable.find(keysym);
> > +  if (it != WinEvents->m_symLookupTable.end())
> > +  {
> > +    return (XBMCKey)(it->second);
> > +  }
> > +
> > +  // try ascii mappings
> > +  if (keysym>>8 == 0x00)
> > +    return (XBMCKey)(keysym & 0xFF);
> > +
> > +  return (XBMCKey)keysym;
>
> keyboard.xml allows to specify those codes. Not returning those would
> break many users remote controls.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/xbmc/xbmc/pull/3505/files#r7241223>
> .
>