On Wed, Dec 01, 2010 at 10:59:11AM +0200, Alexia Death wrote: > On Wed, Dec 1, 2010 at 10:34 AM, Peter Hutterer > <[email protected]> wrote: > > I'm not sure we're talking about the same thing, "forcing reconnect" isn't > > what I would have chosen as wording. > > With the above I meant that once you've configured e.g. ArtPen for the > > Intuos4 with tablet_id 1234, next time this device is detected by the client > > it will automatically issue the commands to auto-hotplug the ArtPen with the > > right configurations - even if the physical device hasn't been detected yet. > > There's no reconnect involved. Is this how you understood it? > No, guess I misunderstood you the first time. However, I have hard > time understanding what it is that you call client? The configuration > tool? Would issuing that command be done by changing ToolSerials > property?
sorry, X nomenclature coming through there. basically, a client is any application but when we're looking at this particular case one that would qualify well is gnome-settings-daemon for the GNOME desktop. it runs in the background, monitors devices and applies their config settings when a new device is detected. with your patch, the ToolsSerials can be configured in the xorg.conf. if we extend that to support properties, we can hotplug devices at runtime. so g-s-d (or any equivalent) would tweak that property to get the new devices hotplugged. > > There is no reason a client can't present the "Wacom Intuos4 6x9 stylus" > > with a tablet ID of 1345 as "Tablet 1". > > Yes, this means syncing between the clients but that's not even that hard. > > Attach the nickname of the device to the device as a property and let the > > other clients read that. And ideally you want the clients to conform to one > > standard here instead of each doing their own thing (also one reason why I'm > > trying to get wacom into GNOME's configuration tools). > If nicknames are to be used then the driver should explicitly have a > property for it. One that user can change through any configuration > tool. Then the full name would become simply an ID, that user need not > worry about. A configuration option like "ToolLabel" that defaults to > the same rules at init as name but is over-ridable both as a base name > and per tool on user side by the user and eventually exposed to > applications and managers would solve this issue. you can already change any property with any client, XACE permitting of course. xinput set-prop --type=int -format=32 <device> "my property" 10 creates a new property "my property" on the device. the same can be done for a nickname/label by any client. the driver doesn't need to know about it since it doesn't do anything with it. Note that all XI calls exclusively work with the device id, not the name. so any client has to do name → ID mapping anyway. I don't think the label should be initialized by the driver either. that a property is missing on a device conveys information already, more so than having the property identical to the device identifier. In this case, the information that the label is missing and thus there is no configuration tool running that assignes nicknames to tablets is quite an important one. Cheers, Peter > Tablets are slightly different from other input devices, because they > always take extra configuration and are always exposed in the UIs as > special tools. When you plug in a muse you generally dont really care > whats it called. there is a single set of mouse configurations and > those are fine for most mice and usecases. not so for tablets. ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
