> So what you are saying is that something like xscribble becomes central
> to input in general on handheld devices: it takes relatively raw input
> and then tells X what to do when it needs to. Building it into the
> core X server seems wrong to me: by definition, we won't get it right:
> I think we should regard it as though it were a window manager: a separate
> application providing some of the UI.
With help from the server for queuing and resending events. One tricky
part will be to get it to work in the presence of server grabs...
> The issue I see is how to arbitrate among more than one application that
> might want/need the high resolution digitizer device...
That's separate from input management, lets see if that can be made to use
the X input extension.
[EMAIL PROTECTED] XFree86 Core Team SuSE, Inc.
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for ++
++ kernel-related discussions. ++
