On Mon, Jan 10, 2011 at 12:10:11PM +0100, Cedric Sodhi wrote:
> On Mon, Jan 10, 2011 at 09:16:14AM +1000, Peter Hutterer wrote:
> > On Sat, Jan 08, 2011 at 11:51:41AM +0100, Cedric Sodhi wrote:
> > > I'm curious whether it would be possible and make sense to implement the
> > > mode in which the pen could be read out so that it's proximity value
> > > (which is currently in no way getting anywhere beyond the driver) is
> > > mapped to pressure (and pressure doesnt matter).
> > >
> > > One of the buttons could enable "spraying" and the position with the
> > > tilt could be calculated to an intercept with the physical pad:
> > >  _
> > >  \\
> > >   \\
> > >    \\
> > >     |¯\
> > >      \½\
> > >       \ \           _
> > >        ¯¯           |-- Proximity
> > >   ‚———————×———————‚ ¯
> > >           ^-- Intercept (calculated from tilt and position)
> > > 
> > > I think it would be very interesting to use the stylus as a natural
> > > airbrush, if that could be done.
> > > 
> > > Maybe an evaluation from one of the professionals (Ping, Peter?) whether
> > > this would be possible at all? If the answer is yes, someone else might
> > > start looking at how in particular this could be done if you guys are
> > > busy with something else.
> > > 
> > > Would make a good feature over the windows driver, no? ;)
> > 
> > should be trivial to export distance through another axis. I'm not keen on
> > mapping it to pressure at all though, easier to add another axis and handle
> > them separately.
> > 
> > Cheers,
> >   Peter
> 
> at first, I'm not even sure that the distance between the pad and the
> tip is exported as a usable value any more. The driver says something
> about CursorProx distance and mentions a default of 10 for the Intuos4,
> but upon further investigating that property the driver than claims that
> such a property does exist of none of the devices.
> 
> Is such a value even exported by the pad? I'm not really sure anymore.

the value is not exported by the X driver currenlty, but it is available
to it. hence CursorProx and whatnot that use this value to fake proximity
events.

> If it happens to be provided, why would you provide it on a separate
> channel? To be frank, I wouldn't see any advantage in using it without
> the according calculation of an intercept and providing latter in the
> primary two channels.

it's a different axis. so instead of x, y, pressure, ... you get x, y,
pressure, distance, ...
that's the correct integration, mix-and-match with other axes will just come
back to bite us in the future..

Cheers,
  Peter

------------------------------------------------------------------------------
Gaining the trust of online customers is vital for the success of any company
that requires sensitive data to be transmitted over the Web.   Learn how to 
best implement a security strategy that keeps consumers' information secure 
and instills the confidence they need to proceed with transactions.
http://p.sf.net/sfu/oracle-sfdevnl 
_______________________________________________
Linuxwacom-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Reply via email to