On Thu, Aug 18, 2011 at 3:04 PM, Peter Hutterer <[email protected]>wrote:
>
> > There are two cases here, I think.
> >
> > 1. Users want to map those wheels/strips to a predefined events, such
> > as keystrokes. We do not need to post the actual values, i.e., no
> valuators
> > are reported. Just emit the keystrokes for them;
>
> as I understand, this isn't something we do now. we always post the raw
> valuators in addition to whatever button/key sequences are assigned. so
> implementing the above would be a behaviour change.
>
No, I didn't want behaviour change. My concern was if clients can still get
the raw or not with the introduction of the scroll axis. The
relative/absolute valuator issue on older X servers has made me worried. So,
we are fine now for this one.
> > 2. Users only want to get the raw values. So, these axes will post raw
> > values instead of scroll events.
>
> This cannot work. we have more than one client and a client can't just
> disable scroll events globally if they don't want them. The new flag means
> that they know which events are emulated and they can then ignore them.
>
Not sure how the app developers and end users will take on this new feature.
Most profeesional users only run one application. And they don't normally
change app when they upgrade OS. If we don't offer a way to turn the scroll
events off for them, they'll have problem to run their favourite app. That's
not good.
Ping
------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilities and model configuration. Take
the hassle out of deploying and managing Subversion and the
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
_______________________________________________
Linuxwacom-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
