[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1193191094.32696.2.camel@moonpix.desrt.ca>
Date: Tue, 23 Oct 2007 21:58:14 -0400
From: Ryan Lortie <desrt@...rt.ca>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: "Zephaniah E. Hull" <warp@...allh.com>,
linux-kernel@...r.kernel.org, Vojtech Pavlik <vojtech@...e.cz>,
linux-input <linux-input@...ey.karlin.mff.cuni.cz>
Subject: Re: [PATCH] Input: Support for a less exclusive grab.
On Tue, 2007-23-10 at 14:10 -0400, Dmitry Torokhov wrote:
> No, rfkill want to see keypresses, period. It does not care if there
> are other applications also seeing the same keypresses, it just does
> not want keypresses stolen from it.
Right. This is exactly the problem. The current grab API exists to
prevent keys from being delivered to normal users, but rfkill still
wants to see them.
No matter how you slice it, if both of these desires are to be satisfied
then there needs to be some sort of a system to differentiate between
rfkill and "normal users". That's what the priority is here.
> Yes, applications need to decide whether they want to process certain
> events or not. But I think that they shodul do it for themselves, not
> for other applications. Otherwise dependencies are just insane and you
> risk to disturb the peace just by adding another piece in the mix.
I disagree. Dependencies aren't a problem at all if people merely rely
on the kernel to take care of the appropriate filtering. Dependencies
only become a problem when X needs to know about "ok... maybe I should
ignore keys that are handled by [hal] [rfkill] [others] etc...".
Cheers
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists