2012-08-02, 16:56
So there will be no way to add command like this in custom keymaps.
The sample I give is clearly a common use case, this is the only way to get Boblight configuration during a movie play to activate / disable the addon.
And there's plenty of other samples this is a one of the most (if not the most) common reason for custom Keymaps.
Limiting the ExecuteAction to a very limited sets seems like a big regression over EventServer.
99% of standard commands in remotes use the same action and already have buttons for them (like OSD, ...) the problem is all the others. If you kill EventServer in the current configuration you also kill lots of functionality in all remotes.
I won't debate about making a 100% custom interface with button labeled as Show OSD on a small phone screen and making this beautiful usable this is not the point.
Or the textbox over a direct keyboard to screen since it's personal point of view.
A little about notifications, on phones / tablets all is about speed / battery usage. And from a widget point of view having a permanent thread waiting for notifications is clearly a non sense you can't start stop register to xbmc on each screen on / off.
While this is the correct way to work with a full remote that is started / closed there's some case like widgets and some other where notifications and synchronous work is not suitable.
But the final point is that it's not because Xbmc was not targeted to use full keyboards or X or Y that users don't have them and like to use them, this is one of the beautifulness of Xbmc to allow users to get the max of their installation, and by wanting to limit a lots on inputs and don't give alternatives you definitively kills a big plus of Xbmc.
The sample I give is clearly a common use case, this is the only way to get Boblight configuration during a movie play to activate / disable the addon.
And there's plenty of other samples this is a one of the most (if not the most) common reason for custom Keymaps.
Limiting the ExecuteAction to a very limited sets seems like a big regression over EventServer.
99% of standard commands in remotes use the same action and already have buttons for them (like OSD, ...) the problem is all the others. If you kill EventServer in the current configuration you also kill lots of functionality in all remotes.
I won't debate about making a 100% custom interface with button labeled as Show OSD on a small phone screen and making this beautiful usable this is not the point.
Or the textbox over a direct keyboard to screen since it's personal point of view.
A little about notifications, on phones / tablets all is about speed / battery usage. And from a widget point of view having a permanent thread waiting for notifications is clearly a non sense you can't start stop register to xbmc on each screen on / off.
While this is the correct way to work with a full remote that is started / closed there's some case like widgets and some other where notifications and synchronous work is not suitable.
But the final point is that it's not because Xbmc was not targeted to use full keyboards or X or Y that users don't have them and like to use them, this is one of the beautifulness of Xbmc to allow users to get the max of their installation, and by wanting to limit a lots on inputs and don't give alternatives you definitively kills a big plus of Xbmc.