We have "Jump if long press" since ages.Thierry wrote:It should be better if this kind of things was available inside EG itself, ie if there is a simple way inside EG to do something different depends if it's short press, long bress, double click or mixte click but it's not the case (or I miss it ?) so ...
And it even allows the user to cascade the setting, so he can have a short press, a one second press and a 4 second press behaviour with the same button and a completely different setup for another button or another context. Double press was never implemented, simply because not many remotes are able to generate such short timings reliable, but it would be possible to implement it as an action the same way as AutoRepeat and JumpIfLongPress of course.
This I actually haven't understood. What should the user do with all the other HID devices (if the remote is not connected) in this list that he would otherwise later have to do in his XML?Same than Short, Long and so on. It's usefull to do something when the remote is not used during a long time and difficult to do inside EG .xml file ...
The ATI Remote Wonder II has a similar zone behaviour (you only can see the zone change when the next button is pressed). I decided to send a zone event in advance if this happens. So if the user changes the zone to 2 and presses the play button for example, he first gets a (one shot) ATI.Zone2 event, immediately followed by an enduring ATI.Play event. This way the user can take advantage of context folders for different zones or use them without regarding the zone or only regard the zones in selected contexts on his decision. So he has all flexibility without worrying if he might take the wrong decision on a "Zone event" checkbox.The remote don't generate a zone event. same than the other, it's avoid to made a big "OR" inside .xml file ...