On Fri, Oct 21, 2011 at 09:17:45AM -0500, Chris Bagwell wrote:
> On Fri, Oct 21, 2011 at 1:46 AM, Peter Hutterer
> <peter.hutte...@who-t.net> wrote:
> > On Thu, Oct 20, 2011 at 12:44:40PM -0700, Ping Cheng wrote:
> >> On Thu, Oct 20, 2011 at 8:03 AM, Chris Bagwell <ch...@cnpbagwell.com>
> >> wrote:
> >> > On Wed, Oct 19, 2011 at 9:10 PM, Chris Bagwell <ch...@cnpbagwell.com>
> >> > wrote:
> >> >> On Wed, Oct 19, 2011 at 7:01 PM, Ping Cheng <pingli...@gmail.com> wrote:
> >> >>> So, we can not rely on pressure to set button 1 click for touch
> >> >>> screen devices.
> >> >>
> >> >> This code shouldn't be needed... or its a bug elsewhere if it is needed.
> >> >>
> >> >> wcmSingleFingerPress() does the below logic but a little better in
> >> >> that it tries not to do a button press during 2 finger gestures
> >> >> (although it has a few known bugs).
> >> >>
> >> >> My touchscreen is doing the left click correctly without looking at
> >> >> pressure. Maybe your seeing something related to pen proximity
> >> >> masking that I didn't consider since my hw doesn't have pen support.
> >>
> >> I'll test it again on my system.
> >>
> >> > Since your working in this area, let me repost a related open issue.
> >> > Maybe you'll have time to work on it.
> >> >
> >> > If you use MyPaint application with the touchscreen you've got
> >> > (without pressure that is), it won't work.
> >> >
> >> > The reason is because that application ignores left click and instead
> >> > relies only on pressure values. Or at the least, its setting ink to
> >> > fully transparent when pressure is reported as zero. Since MyPaint
> >> > works with mice, I think it must only do this when a pressure axis is
> >> > reported.
> >> >
> >> > So I think we need some code in our init phase that only declares
> >> > pressure axis when maxZ != 0.
> >>
> >> This requires an interface change. We will need to only report 2
> >> valuators, x and y. That might be fine with newer X server and Gtk
> >> versions. But, I guess we'll need to deal with backward compatibility
> >> issue. I am not sure how we want to handle it.
> >> ..
> >
> > what other axes are on this device? if it's just 2 anyway this is a
> > nonissue. if there are other axes we need to rely on the client to determine
> > which axis represents what anyway (already the case for XI 1.x)
> >
>
> I haven't came up to speed on application side or if server can handle
> wholes in valuator lists and why I haven't submitted anything yet. I
XI2 handles it on the protocol side,, the server should be able to handle it
nowadays too though that code has not seen much exposure yet. note that to
use this in the wacom driver would mean either ifdef hell or dropping
support for older server versions since currently we're still using the old
input apis.
> can kinda supply info on whats being advertised for multi-touch
> touchscreens; my touchscreen is in the mail somewhere. It should look
> like my Bamboo touch if it was in absolute mode.
>
> Things I note from below output that I hope get addressed at some point:
>
> 1) My device advertises Pressure support with range of 0-4096 but
> never sends anything. If I was an application writer (I'm not, BTW,
> so could be wrong :-) ), I would make assumptions when I saw that
> valuator declared. I'd stop looking for left click and instead start
> looking for some non-zero pressure value as left click.
that sounds like a kernel bug. the device shouldn't advertise the axis
if it doesn't use it (possibly quirked out if the HW is at fault)
> 2) My device does not support Tilt but it claims it does. It never
> sends anything obviously. Less of an issue since 0 tilt will look
> same as no tilt support to an application (?). But it would be nice
> if we didn't advertise it so that any tilt related menu options can
> correctly be greyed out.
same as above
> 3) There are 2 "Abs Tilt Y" labels. The second one is because we do
> not have an else {} to fall into for devices that do not have absolute
> wheels and do not skip the Init of that Valuator. I've no idea how
> applications would deal with this... Probably just ignore one of the
> two. Nothing is crashing today so I guess they are dealing with
> it/ignoring all tilts.
that's a driver issue, the axis labels aren't quite bug-free. could be
fixed, just haven't found the time for it yet.
Cheers,
Peter
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
