Difference between mouse driver and digitzer driver RRS feed

  • Question

  • Hi Kernel Experts:

    I have a question regarding touch coordinate reporting on a system with multiple touch monitors:

    I have a mouse filter driver which can report/translate a touch point correctly no matter which touch monitor is touched. A touch is reported up to the system (MouHid.sys) in 64k virtual desktop coordinates.

    But when working with a digitizer touch filter driver (report to MsHidKmdf.sys), the above approach seems no longer works: even though a touch is converted to 64K coordinate and then report to lower layer, but the final result is that the cursor is always stuck at the lower-right corner of the primary display monitor and not moving to the correct touch monitor. In debugging , I can see the touch coordinate is reported correctly in 64k range.

    Not sure what I have missed, any opinions/ideas is much appreciated.

    Thanks in advanced.


    Saturday, February 2, 2013 6:17 PM

All replies

  • Perhaps digitzer input is not absolute data, relative instead?

    d -- This posting is provided "AS IS" with no warranties, and confers no rights.

    Saturday, February 2, 2013 8:57 PM