Hi Cedric,
I'm probably misunderstanding what you are asking. But you can use
Options with the same syntax as in xorg.conf in xorg.conf.d. e.g.:
Option "Button2" "3"
Option "TopX" "0"
After the Driver line in the relevant snippet. Maybe you're running
into the the fact the udev currently can't configure dependent
devices? Like the early days of HAL before wacom-to-hal. I'm pretty
sure that's been addressed upstream. Peter gave an example snippet
for a dependent device a while ago. He can tell us when to expect it.
I actually thought it might be in 1.9.
In the meantime you have to use xsetwacom scripts or the xorg.conf for
dependent devices.
Favux
On Wed, Jan 26, 2011 at 2:04 AM, Cedric Sodhi <[email protected]> wrote:
> Hello Peter,
>
> could you tell us how in particular udev can set Properties? I've been
> very concerned with this topic for quite a while and in the end I had to
> conclude that it's *not* possible to use udev in the same manner as hal
> used to work.
> I did *not* find any way to communicate settings to xorg apart from
> manually xauthing and using xset/xinput to do that.
>
> If you know how udev (possibly to custom attributes) can configure xorg
> please explain it!
>
>
> On Wed, Jan 26, 2011 at 03:53:05PM +1000, Peter Hutterer wrote:
>> On Tue, Jan 25, 2011 at 09:06:18PM +0100, Cedric Sodhi wrote:
>> > Hello, this is the same for all devices, I think. At least it's the same
>> > for my Intuos4. But I think that's okay.
>>
>> it's the same for all devices and can largely be blamed on wacomcpl.
>> wacomcpl changes X input properties which are only valid for the lifetime of
>> the device. wacomcpl is essentially a fancy version of the "xinput" or
>> "xsetwacom" tools (in fact, wacomcpl uses xsetwacom).
>>
>> for permanent storage, the tool needs to either reapply the settings
>> whenever a new device was detected or write them to permanent storage
>> (xorg.conf or in newer servers xorg.conf.d).
>>
>> > It's not the responsibility of the driver to re-initialize the device
>> > with the old settings - the driver is simply the method to communicate
>> > with it, it shall not offer any "special service" such as remembering
>> > options. You should use a dedicated tool for that.
>> >
>> > There is a certain problem though, which, however, is not to blame on
>> > the wacom but rather on X11 polcies, that is, usually UDEV should handle
>> > hotplugging these days but udev (or anything started from it) will have
>> > problems with setting xinput props because it lacks the authz to do so.
>>
>> udev (and HAL) can both set options from their respective configuration
>> files. In fact, servers 1.5, 1.6 and 1.7 need HAL's fdi configuration for
>> input.x11_driver and input.x11_options.
>>
>> these options are permanent and apply to hotplugged devices as well.
>> wacomcpl doesn't talk that configuration though.
>>
>> Cheers,
>> Peter
>>
>> > I suggest you set up a simple bash script which is started with xinit
>> > and will listen for the wacom being plugged or not. Most easily, you
>> > could do this by setting up an udev rules which provides a user-readable
>> > switch (such as a file /tmp/wacom_is_plugged) when the wacom is up and
>> > removes it if it isnt.
>> >
>> > The bash script can simply run in a loop (with sleep 1000 or so) and
>> > execute your wacom_set_props.sh script if udev communicates it that the
>> > device has been plugged.
>> >
>> > I've a similar setup (not for the wacom but for an external) monitor and
>> > it works flawlessly and, best of all, is very flexible.
>> >
>> > regards,
>> > Cedric
>> >
>> > On Tue, Jan 25, 2011 at 11:48:53AM -0800, Steven L. Seed wrote:
>> > > Has anyone noticed that when you hotplug a Cintiq that has been
>> > > calibrated
>> > > with the wacomcpl, you lose the calibration (it resets) after you
>> > > hotplug
>> > > the tablet? This is particularly problematic in our environment where
>> > > the
>> > > tablets are attached via kvm switches to work with multiple systems.
>> > > We
>> > > are on RHEL6 running Xorg 1.7.7-26 and the wacom driver version
>> > > 0.10.5-8.
>> > >
>> > > --
>> > > [1][IMG]
>> > >
>> > > References
>> > >
>> > > Visible links
>>
>> ------------------------------------------------------------------------------
>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
>> Finally, a world-class log management solution at an even better price-free!
>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
>> February 28th, so secure your free ArcSight Logger TODAY!
>> http://p.sf.net/sfu/arcsight-sfd2d
>> _______________________________________________
>> Linuxwacom-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Linuxwacom-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Linuxwacom-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
