All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@insightbb.com>
To: "Zephaniah E. Hull" <warp@aehallh.com>
Cc: "Magnus Vigerlöf" <wigge@bigfoot.com>,
	linux-input@atrey.karlin.mff.cuni.cz,
	linux-kernel@vger.kernel.org
Subject: Re: input: evdev.c EVIOCGRAB semantics question
Date: Sat, 12 Aug 2006 20:00:47 -0400	[thread overview]
Message-ID: <200608122000.47904.dtor@insightbb.com> (raw)
In-Reply-To: <20060812165228.GA5255@aehallh.com>

On Saturday 12 August 2006 12:52, Zephaniah E. Hull wrote:
> I can dust off the masking patch sometime here if Dmitry thinks that
> he'd be willing to see a second method for this in addition to grabbing,
> adding support to xf86-input-evdev would be trivial, and the same could
> probably be said for the wacom driver that does grabbing at the moment.
> 

I would not mind if we get it working right ;) Do we need to turn off
"undesirable" handlers or do we want to limit output to one particular
handler? I'd prefer the former, if possible. Do we keep a counter or
set of counters so several processes can mask output, etc. Can we keep
event delivery somewhat fast? 

-- 
Dmitry

  parent reply	other threads:[~2006-08-13  0:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-12 15:24 input: evdev.c EVIOCGRAB semantics question Magnus Vigerlöf
2006-08-12 16:52 ` Zephaniah E. Hull
2006-08-12 21:06   ` Magnus Vigerlöf
2006-08-13  0:00   ` Dmitry Torokhov [this message]
2006-08-13  3:28     ` Zephaniah E. Hull
2006-08-14 14:20       ` Dmitry Torokhov
2006-08-14 14:28         ` Zephaniah E. Hull
2006-08-14 15:00           ` Dmitry Torokhov
2006-08-14 16:04             ` Ian Stirling
2006-08-14 16:09             ` Zephaniah E. Hull
2006-08-14 16:22               ` Dmitry Torokhov
2006-08-14 14:58         ` Mattia Dongili
2006-08-14 15:15           ` Dmitry Torokhov
2006-08-14 22:49             ` Magnus Vigerlöf
2006-08-15 11:51               ` Magnus Vigerlöf
2006-08-15 23:20               ` Magnus Vigerlöf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200608122000.47904.dtor@insightbb.com \
    --to=dtor@insightbb.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=warp@aehallh.com \
    --cc=wigge@bigfoot.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.