On Fri, Nov 5, 2010 at 07:49, Jonathan Gordon <jdgo...@gmail.com> wrote:
> I hit this issue with the recent android button handling reworking. > not sending a BUTTON_REL is only a problem is the button can cause a > context (screen) change. So, how can that happen with the scroll > wheel? If you reach end-of-playlist after having used the wheel, then last_button in action.c is a wheel event, without a release. A long long press on play/pause to stop playback can trigger it too (I'm guessing due to queued repeat events from after the WPS has started stopping), at least if an auto-bookmark is created. But I just realized my patch only fixes the second case. Maybe action.c needs to ignore wheel events in last_button in the if statement I mentioned earlier... -- Magnus
