XChangeDeviceControl/XGetDeviceControl ?
Daniel Stone
daniel at fooishbar.org
Tue Apr 18 00:37:00 PDT 2006
On Tue, Apr 18, 2006 at 11:40:20AM +0400, Andrew Zabolotny wrote:
> On Tue, 18 Apr 2006 00:57:43 +0300
> Daniel Stone <daniel at fooishbar.org> wrote:
> > If there are hundreds of such structures, we're already doing
> > something wrong. What use cases do you have in mind?
>
> Well, here are the parameters for Wacom tablets:
>
> XWACOM_PARAM_TOPX
> XWACOM_PARAM_TOPY
> XWACOM_PARAM_BOTTOMX
> XWACOM_PARAM_BOTTOMY
>
> These four already fit in a separate structure, like DEVICE_ACTIVEAREA
> or something like this.
>
> XWACOM_PARAM_DEBUGLEVEL
>
> This one doesn't make sense to be put into any other structure?
> So a separate DEVICE_DEBUGLEVEL? :-)
I don't really think it makes sense to be user-configurable, at all.
Why not just use the standard levels provided you, and launch the server
with -verbose and -logverbose?
> XWACOM_PARAM_PRESSCURVE
> XWACOM_PARAM_RAWFILTER
> XWACOM_PARAM_MODE
> XWACOM_PARAM_SPEEDLEVEL
> XWACOM_PARAM_CLICKFORCE
> XWACOM_PARAM_ACCEL
> XWACOM_PARAM_XYDEFAULT
> XWACOM_PARAM_GIMP
> XWACOM_PARAM_MMT
> XWACOM_PARAM_TPCBUTTON
>
> Well, with a big strain we can put all of the above into a single
> structure, but this will introduce an additional level of complexity
> like parsing masks or checking for -1 (DONTCHANGE flags) and such.
>
> XWACOM_PARAM_BUTTON1...XWACOM_PARAM_BUTTON32
>
> These definitely belong to a different structure, like
> DEVICE_BUTTONACTIONS, and again there's the problem that you can't
> change a single button assignment at a time. Right now it's simple:
> call XChangeDeviceControl with DEVICE_RESOLUTION,
> resolutions [0] = XWACOM_PARAM_BUTTONX; resolutions [1] = action;
> and you're done.
What exactly do they do? Is there no way you can fit this into the
existing button map paradigm?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 191 bytes
Desc: Digital signature
URL: <http://lists.x.org/archives/xorg/attachments/20060418/115727c8/attachment.pgp>
More information about the xorg
mailing list