Add a button 'name' field to the database

[njh]

Hello,

Please could you add a 'name' field to the button database and setup wizard? This would make it much easier to identify buttons and avoid having to store button names separately.

The Node-RED node currently stores a button name to device ID association in JSON.

Thanks,

nick.

[Emill]

You basically want to be able to store custom data for each flic in the daemon's internal db?

Can't you map the bd address to custom data and store that in your own db or is that problematic in some way? Den 8 aug 2016 12:38 skrev "Nicholas Humfrey" notifications@github.com:

Hello,

Please could you add a 'name' field to the button database and setup wizard? This would make it much easier to identify buttons and avoid having to store button names separately.

The Node-RED node currently stores a button name to device ID association in JSON.

Thanks,

nick.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/50ButtonsEach/fliclib-linux-hci/issues/27, or mute the thread https://github.com/notifications/unsubscribe-auth/ABlXavhqwFydiaqZ4qVjAIOY72OdEvUOks5qdwchgaJpZM4Je6ig .

[njh]

Not custom data, no. If it was application specific, then I would indeed stick it in my own store.

But I think a human readable name/label of the button is useful, across a range of applications, to work out which one is which.

It would make building a UI much easier - when presented with a list of buttons registered with flicd, to know which one is which. And once they are named centrally, you can work with those names across multiple clients and multiple implementations.

[Emill]

So you mean a name defined by the user? Like in our iOS and Android apps?

2016-08-08 13:54 GMT+02:00 Nicholas Humfrey notifications@github.com:

Not custom data, no. If it was application specific, then I would indeed stick it in my own store.

But I think a human readable name/label of the button is useful, across a range of applications, to work out which one is which.

It would make building a UI much easier - when presented with a list of buttons registered with flicd, to know which one is which. And once they are named centrally, you can work with those names across multiple clients and multiple implementations.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/50ButtonsEach/fliclib-linux-hci/issues/27#issuecomment-238214290, or mute the thread https://github.com/notifications/unsubscribe-auth/ABlXak1vvf9AJt6QG3Q0snJwolVZnhpvks5qdxjrgaJpZM4Je6ig .

[njh]

Yes, just like that :)

[CheapB]

+1