On Sun, Nov 28, 2010 at 10:15:25PM +0200, Alexia Death wrote: > > If I had a tablet with multiple tools, I'd think the general concept > > is very important to me as well. I'd also want it to work without > > config file magic if possible (GUI would be OK). > Well, that gui would need a persistent way to store those settings for > the driver to have them available at load. This is what this provides. > > > So I'm wondering if we could do something like monitor serial #'s > > coming in for protocol 5 devices and when we see new ones we could > > hotplug at that time. There may be a slight delay caused by this and > > so your solution would probably be the complement to pre-hotplug when > > you know your serial #'s. > This might be possible and even optionally welcome, but needs to be > thought through carefully. For example, then you can just leave off > automaticaly creating the base devices because no event would ever > pass them, since each tool presented presents a new spawned device. > Also, at least for starters, such behaviour should be optional, > because GTK2 applications, meaning most of the current graphics > software on linux, cant cope with on the fly devices. GTK3 will be > able to allow that however. What will remain given is that users will > want to name their devices. so even when autospawing a way to specify > a name for serial and possibly even for the base device would be > needed.
in principle, I support Chris' suggestion but as a word of warning there's a bit of a configuration issue involved with this. We see the serial number only when the first event comes in. So we hotplug, and send the events. A client can only apply device-specific configuration (run-time like in gnome-settings-daemon, not xorg.conf) after it has seen the device, so the first events will be sent without the configuration in place. There isn't really a way to get around this and it has the potential to cause confusion. 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. > > If we do that then it kinda leads the way for what tool names should > > be. We can convert BTN_TOOL_AIRBRUSH/ARTPEN/etc that came with serial > > # to create string to insert: > > > > Wacom Intuos3 6x8 stylus STYLUS <-- pre-hotplugged when tablet detected > > Wacom Intuos3 6x8 airbrush stylus STYLUS <-- hotplugged only when tool seen. > > Wacom Intuos3 6x8 artpen stylus STYLUS <-- hotplugged only when tool send. > This wont work, even if you can differentiate airbrushes/artpens from > regular ones. Im not sure if you can, I dont know the protocol well > enough. My current example didnt show it, but I also have 2 regular > grip pens I intend to configure as separate devices with their own > nicknames. I just left them out for testing serial reporting on main > devices. And this is actually a very common case. Two identical pens, > two different devices/settings in graphics applications. Pens are > marked for example by putting piece of blue electrical tape around one > and red around another. > > > I can provide some rough psuedo-code if your interested in pursuing this > > option. > > > > There is some issues if you have 2 stylus that map to same BTN_TOOL_* > > but probably your usecase is most common? > See above for use cases. However enabling spawning devices on the fly > in general I'm very much interested in. > > > As for the long names, they are a little bit of pain but my hope is we > > never really use them directly. I mean no config files needed; no > > xinput or xsetwacom needed; just some GUI's that show device names in > > drop down list. > It's the GUIs where long names are causing the pain. If you can, try > out the GIT version of GIMP. It provides a sidebar interface with tool > names listed so you can manage both the tools that are available now > and all other devices that have been around in the past. It just about > exactly fits the current base name for my Intuos3 with the tool type, > appending anything else would hide the significant part force me to > scroll the list... And Im not sure that wide drop-downs are much > better. maybe a drop-down menu just isn't the right widget then? :) 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
