[MPlayer-dev-eng] [PATCH] Apple Remote support double click

[Ulion]

>
> How come no other input device has ever required huge invasive changes
> to support? Either this patch is just badly written and not doing
> things right, or Apple's API is nonsense. Moreover the whole idea of
> delaying the processing of a first click in order to make sure it's
> not a doubleclick is stupid and counterintuitive. In every other
> application I've ever seen, a doubleclick functions as additional
> behavior on top of what a single click already did...

I'd like to keep doubleclick action on the base of singleclick actions
also. But, apple remote only have 6 bottons, there are too many common
commands users needed. There are only few commands can work together
for the doubleclick action base on singleclicks actions. Besides
doubleclick for toogle_fullscreen (which can work fine with play/pause
commands produced by singleclicks of play button),  only way to
support most other commands is to simulate doubleclick, and delay or
ignore singleclick. Any idea on this?

>
> I've also been told (out-of-band) by others reading this patch that
> either the API is horribly broken or else the patch author is not
> using it right. Either would be a perfectly good reason for rejecting
> the patch, but if it's fixable I'd be happy to see it fixed and
> included. However I will not be happy to see more broken stuff
> included in MPlayer. We already have way too much broken stuff...
>

I'd like to hear what's the broken API, or how to using it in right
way, then I can fix it. By now I have no idea about what's the
'others' refered.

-- 
Ulion