On Mon, Aug 04, 2014 at 03:04:06PM +1000, Peter Hutterer wrote:
On Sun, Jul 27, 2014 at 11:28:28PM +0200, Jonas Ådahl wrote:
The kernel may send a 'release' event without ever having sent a key
'pressed' event in case the key was pressed before libinput was
initiated. Ignore these events so
On Sun, Jul 27, 2014 at 11:28:28PM +0200, Jonas Ådahl wrote:
The kernel may send a 'release' event without ever having sent a key
'pressed' event in case the key was pressed before libinput was
initiated. Ignore these events so that we always guarantee a release
event always comes after a
On Mon, Jul 28, 2014 at 10:03:25AM -0700, Bill Spitzak wrote:
On 07/27/2014 11:48 PM, Ran Benita wrote:
Hi Jonas,
On Sun, Jul 27, 2014 at 11:28:28PM +0200, Jonas Ådahl wrote:
The kernel may send a 'release' event without ever having sent a key
'pressed' event in case the key was pressed
Hi Jonas,
On Sun, Jul 27, 2014 at 11:28:28PM +0200, Jonas Ådahl wrote:
The kernel may send a 'release' event without ever having sent a key
'pressed' event in case the key was pressed before libinput was
initiated. Ignore these events so that we always guarantee a release
event always comes
On Mon, Jul 28, 2014 at 09:48:05AM +0300, Ran Benita wrote:
Hi Jonas,
On Sun, Jul 27, 2014 at 11:28:28PM +0200, Jonas Ådahl wrote:
The kernel may send a 'release' event without ever having sent a key
'pressed' event in case the key was pressed before libinput was
initiated. Ignore these
On 07/27/2014 11:48 PM, Ran Benita wrote:
Hi Jonas,
On Sun, Jul 27, 2014 at 11:28:28PM +0200, Jonas Ådahl wrote:
The kernel may send a 'release' event without ever having sent a key
'pressed' event in case the key was pressed before libinput was
initiated. Ignore these events so that we
The kernel may send a 'release' event without ever having sent a key
'pressed' event in case the key was pressed before libinput was
initiated. Ignore these events so that we always guarantee a release
event always comes after a pressed event for any given key or button.
Signed-off-by: Jonas