[binco]

I'm using an Packard Bell Viseo Touch 200 (0408:3000 Quanta Computer, Inc. Optical dual-touch panel) connected to a Raspberry Pi and faced the issue described here: http://www.raspberrypi.org/phpBB3/viewto...0&p=143195

After patching XBMC with the following, the Button Code is recognized:

Code:

diff --git a/xbmc/input/linux/LinuxInputDevices.cpp b/xbmc/input/linux/LinuxInputDevices.cpp
index 3d66083..b723120 100644
--- a/xbmc/input/linux/LinuxInputDevices.cpp
+++ b/xbmc/input/linux/LinuxInputDevices.cpp
@@ -519,7 +519,7 @@ bool CLinuxInputDevice::KeyEvent(const struct input_event& levt, XBMC_Event& dev
     devt.button.x = m_mouseX;
     devt.button.y = m_mouseY;

-    switch (levt.code)
+    switch (code)
     {
       case BTN_RIGHT:
         devt.button.button = XBMC_BUTTON_RIGHT;

Additionally I had to add this to my mouse.xml to get rid of the Message "ProcessMouse: trying mouse action mousedrag" since the touchscreen is too inaccurate, so that every click gets recognized as a drag operation.

Code:

<keymap>
  <global>
    <mouse>
      <mousedrag>leftclick</mousedrag>
    </mouse>
  </global>
</keymap>

Do you have any suggestion to make this better and optionally get right click working?

[betz0r]

could you apply this patch to git sources?
i don't even understand how that patch works but for sure the developers will do and will perhaps talk about importing it to the major releases? Would do me a nice favour so i don't have to recompile xbmc on my raspberry pi...