Martin, On Tue, Jan 19, 2010 at 22:57:50 +0100, Martin Pitt wrote:
> Julien Cristau [2010-01-19 22:43 +0100]: > > Hrm. This means with inputclasses we'll need one inputclass section for > > each device type. Or tag the devices we don't want to handle somehow in > > the udev db. > > I'm afraid I don't quite understand this. AFAIUI, the input classes > will look directly at the udev properties, and the x11_* properties > will be dropped completely. But Peter's proposal [1] already has > MatchIsKeyboard, MatchIsPointer, MatchIsJoystick, and the like. So am > I missing something, and this isn't enough for some reason? > > (For this particular bug we should probably not do the > "evdev-catchall" thing, though.) > Right, what I meant to say was that we won't be able to just use a catchall inputclass, we'll have to use one section with MatchIsKeyboard, one with MatchIsPointer, and so on for each device type (matches within one section are ANDed). I find this a bit less pleasing, but it will still work, so it's probably not a huge problem. Cheers, Julien -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
