Forgot to copy list. On Mon, Jan 11, 2010 at 2:26 PM, Ping <[email protected]> wrote:
> On Mon, Jan 11, 2010 at 12:09 PM, Chris Bagwell <[email protected]> > wrote: > > > > > > On Mon, Jan 11, 2010 at 12:17 PM, Ping <[email protected]> wrote: > >> > >> > The reason I split them is because the CapacityDefault change is > minimum > >> > requirement to get a usable Bamboo P&T (that unwanted button click is > >> > hard > >> > to work around) and has no work around such as via xsetwacom since it > >> > seems > >> > to be used to indicate internally detected hardware features. > >> > >> > >> Unwanted button click can be ignored by only turning on the left-click > >> by the second touch event only when it is perfomed within a certain > >> time interval with the first touch. That is, a double touch selects an > >> object. A single touch only moves the cursor. Those can all > >> implemented under /* process single finger events */ in wcmCommon.c > >> after dusabling left-click in wcmUSB.c. Please discuss this with > >> Jason Childs. He is working on the same feature as you do. Two sets > >> of eyes are better than one, usually :). > >> > > > > I agree with needed changes (at least I want those changes) but can you > > comment on the following? I believe when you say "selects an object" you > > mean button press like Tablet PC mode is doing today for single touch. > The > > Bamboo P&T is considered a capacitive device, correct? So when we update > > Yes, Bamboo P&T is a capacitive device. However, > > > software such that a single touch moves arrow and double touch presses > > button should the button press only occur if threshold is above value > > computed by Capacity? > > the Capacity value reported doesn't have the accuracy to serve the purpose. > OK... I started to realize that after sending email. At least I realized what is happening is that value reported is never crossing threshold to be considered a button press and thats why I'm seeing the behavior I want (no button press). > > > If we still want that feature then I believe the original patch is still > > required. If we do not want that feature then I guess minor man page > > updates are needed to reflect Capacity value default to -1 for some > > capacitive touch devices. > > It is not a question of what we want. It is a question of what we can > :). Are you convinced? > Yep, I'm convinced. So as apart of this, I'll eventually submit a patch that updates the man pages to mention that Capacity defaults to -1 on Bamboo P&T touch devices and is not referenced. This will mainly be to prevent people mucking with that thinking it should change behavior on these devices. I'll email Jason and see how he is coming along and if there is any way to split the work load up. Chris
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
