Analogously in the case of GUI toolkits, one would usually act on a button release, but only if it was preceded by a button press. The app however could encounter a press without a release (mouse dragged off the button) or a release without a press (mouse dragged onto the button). In the former case the button is informed that the press has been cancelled (by the pointer leaving) before it was released. And in the latter case the button simply ignores a 'release' that had no press before it. So there's another precedent for button cancellation of sorts...
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1547864 Title: libinput doesn't handle EV_KEY event with a value of 255 (BUTTON_CANCLED), to support Android home buttons To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1547864/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
