Hi, I've created a fork of the driver for legacy serial protocol IV tablets made by Julian Squires (more info can be found in older posts in this mailing list, and at http://cipht.net/2011/07/02/wacom_serial-initial-release.html).
I have a question regarding implementing the two available channels in protocol V. Currently, I just send all the tool data of a channel within a single "sync window", together with the appropriate BTN_TOOL_* set to 1. There is only one such BTN_TOOL_* per sync window. I don't explicitly reset the other tool's BTN_TOOL_* to 0 in that window (because it can still be in proximity at that moment). Is this the proper way to implement it? I had a look at wacom_wac.c, and that seems to follow the same approach, as far as I can tell. Is there any way I can verify that both channels are working correctly? What kind of behaviour should I expect, exactly? Note: I dont sent ABS_MISC (as requested for the generic interface(?)), but I do send a MSC_SERIAL command every sync window for the appropriate tool. If you want, you can have a look at the code at http://github.com/RoaldFre/wacom_serial5 -- Note: it's still *very* WIP and needs tidying up. Roald (roaldfre) ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
