Re: mousedev patch

[Vojtech P. <vo...@su...>]

On Sun, Jul 29, 2001 at 01:21:29PM -0700, Charles Duffy wrote:
> On Sun, Jul 29, 2001 at 08:31:38PM +0200, Vojtech Pavlik wrote:
> > On Tue, Jul 24, 2001 at 08:21:43PM -0700, Charles Duffy wrote:
> > > Thus, I'd like to have this be Correct Behaviour for an event handler.
> > > (Some changes are also needed to tsdev.c; I'd be glad to provide
> > > them).
> > 
> > I think much better would be letting mousedev know both the correct
> > screen and touchpanel resolution.
> 
> Yes, if the information is available. If it isn't, it makes sense for
> an event handler to attempt to function nevertheless rather than give
> up utterly.

I agree with the changes to mousedev (and/or tsdev) because they make it
more robust.

But this is *not* a reason to omit setting the absmin/absmax in the
touchscreen driver.

> It also doesn't make sense to require the device
> generating events to ask the user for numbers which aren't otherwise
> available to it if in most application those numbers will serve no
> purpose.

Yes. But it would definitely be nice if it could get the numbers from
the console subsystem - in many cases they are known. Namely on
handhelds.

By the way, now that we have tsdev, perhaps support for abs values in
mousedev could be dropped completely, because X will be able to read
even say USB tablets via the tsdev device as absolute values?

> Thus, while I agree that an event generator should be as strict as
> possible in what it generates -- providing resolution numbers if at
> all available -- an event handler should still be able to Do The Right
> Thing (or the closest possible approximation) if the numbers just
> aren't there.

It's good we agree perfectly then.

-- 
Vojtech Pavlik
SuSE Labs