Another handy trick used in GUI toolkits is to introduce a "clicked" event created by the toolkit. So simple apps don't need to track button states, only listen for the 'clicked' event and ignore all other events. So a button might receive any of these sequences of events:
press -> appearance changes to depressed press, release, clicked -> appearance resets and action triggered press, cancelled -> appearance resets release -> nothing happens but typically an app only really needs to act on 'clicked'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
