globalist

Show button mappings?

4 posts in this topic

Posted (edited)

So in the Flirc config program where it's showing the layout of your virtual controller, it's the most logical thing to expect to see which buttons of your virtual controller are already mapped (and possibly, also to what, using maybe IR codes from your physical remote for idtentification). Why doesn't the software actually show this important info?

Edited by globalist

Share this post


Link to post
Share on other sites

It does.   With your Flirc plugged in, and the app running, point your remote at the sensor and press a button that is already bound.  The keyboard button, that the remote button is bound to, will light up on screen.

Share this post


Link to post
Share on other sites

It does indeed. But why not save us the hassle and highlight all the mapped buttons from the get go (or keep them highlighted as you add new ones)?

Share this post


Link to post
Share on other sites

Highlighting would be nice but it's not universally representative. For example it would not work very well for full keyboard controller. If you have few buttons recorded with modifiers (shift, ctrl etc) and all assigned button were to be highlighted, then how would you recognise which buttons had been assigned with modifiers and which not?

Don't thing I'm against such functionality. It would be really helpful, but I think it would need to be more universal. Maybe a dialog containing a table with assigned keys. It would then highlight keys when hovered or clicked on specific line. Also Flirc itself doesn't store an information on which controller you've recorded a key (whether it was on Kodi, FireTV or Full Keyboard). It only stores a HID keycode with optional modifier and a hash code derived from an IR signal. So the table would rather display letter X for example instead a Kodi's  Stop function in such table.

Also you can already display such a list of assigned keys but not in GUI. When you've installed Flirc software, besides the GUI app you've also installed a command line util called flirc_util. If you're using Windows then you need to open command line windows (Win + R, enter cmd.exe and press enter, for example), then change the directory to where you've installed Flirc and then you can execute:

flirc_util.exe keys

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now