On 1/12/10 17:37 , Alexia Death wrote: > On Wed, Dec 1, 2010 at 5:48 AM, Peter Hutterer<[email protected]> > wrote: >> Of course, one of the cool things you could do then is have a UI popup "new >> tool found, do you want to configure?" and then force device hotplug through >> Alexia's solution (albeit with properties) whenever the tablet itself is >> detected. > That was the way I thought this could evolve. The tool-serials > configuration reused. But forcing tablet reconnect is no good for the > artist. Perhaps, If tool serials property is changed, the tools that > were removed should be removed and tools that were added added. Or if > removing is tricky, adding on the fly would be enough.
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? >> maybe a drop-down menu just isn't the right widget then? :) > No sane widget can handle many that long names well. The only > alternative is that applications will treat this as an ID, and let > users assign nicknames for them. Sort of confusing if you need to sync > your painting app and your configuration app on names, but a > sane/humanly usable name length ends at 25 characters. Ive also been > wondering, what happens If I plug in a second identically sized and > branded tablet. I don't own two and its not very practical case, but > it sort of shows that the driver should still worry about making names > unique and not take away the ability to name your devices you have > when you do static configuration. Honestly, it would be more usable if > the format of the default basename was "Wacom-%d", where %d is tablet > ID/model ID. For configuration association, it should be related to > the model, but the whole brand/modename/size combo as as string is > sort of pain. We expose this information to the clients and I think this should be enough. Trying to second-guess the information we get from the X server (in the driver we don't know where the name is coming from) is a bad idea, it makes the behaviour unpredictable. AFAIK, the brand/modename/size combo comes straight from the hardware. if the tablet is statically configured, then the name is whatever the user chose. In the driver, we don't know the difference. 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). Cheers, Peter ------------------------------------------------------------------------------ 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
