Ahah… I think it’s all clear to me now. This is an excellent explanation.
So can’t you just use that?
Mappings could probably be added. I think also maybe that the JME built-in remapping might let you map those to buttons again but I’m not sure. It could be no.
Lemur really wanted to present a standard minimal view which is probably why I didn’t add a way to easily add your own mappings. The idea was that if you have JME properly configured then your Lemur UI would always work as expected. That’s probably no excuse for not letting you map your own if you wanted to, though… and just know that it will maybe not work right for others.
As it is, if you want to customize the mapping then the only options are:
- modify Lemur code
- extend InputMapper and override the mapGamepad(Joystick j) method.
…which then if you use standard lemur and not InputMapper on its own means that you have to extend GuiGlobals also, I think… Hmmm… no that won’t work either. If you are using GuiGlobals then it will always use the stock InputMapper.
I really need to add some mapping methods to InputMapper. If you are impatient then you can do it locally if you have Lemur checked out. If you use gradle/maven in your own project then it’s pretty easy. Just “gradle install” lemur locally and then your other builds will pick up your local version.