Rob Shortt wrote: > Dirk Meyer wrote: >> Rob Shortt wrote: >>>Log: >>>Add DIRECTFB_MAP. I would like to move this into the plugin's config() but >>>until we get to do more work on integrating plugin configs into the new >>>config format this will lead to problem. >> >> >> When we move to kaa.canvas, maybe this needs to go into >> kaa.display. Or maybe this whole code needs to be in >> kaa.base.input. But since it is not that special to freevo, I guess it >> should be in kaa. A nice idea would be to have a unique key mapping, >> both x11 and dfb should return the same values. > > I haven't really looked at kaa.base.input but I think this code should > probably go there. I also don't like the idea of different keymaps from > a user's perspective so I'll revisit that at the same time.
It would be nice to have the same names for X11 and DFB (maybe also FB
or SDL in the future). I like the stuff Tack did for x11: always
return a string ('a', 'b', 'c' .... 'f1', 'enter', ...). That also
works for other inputs like bluetooth ('1', '2' ... 'hang up' ...) and
gamepad ('up1', '1', '2', ...'12', '13' ...). BTW, the x11 keycode
stuff is in kaa.display, maybe you want to put it into
kaa.display.dfb. If you always return a string, the user does not need
to have access to the internal map.
Dischi
--
There are very few problems that cannot be solved by orders ending with
'or die.' - Alistair J.R. Young
pgp8zsZBkB1Nm.pgp
Description: PGP signature
