Bug 1227 - LinuxEventDeviceTracker reports misaligned relative Mouse Coordinates when using NEWT w/ RaspPi 7" TFT
Summary: LinuxEventDeviceTracker reports misaligned relative Mouse Coordinates when us...
Status: CONFIRMED
Alias: None
Product: Newt
Classification: JogAmp
Component: embedded (show other bugs)
Version: 2.4.0
Hardware: embedded_arm linux
: --- enhancement
Assignee: Xerxes Rånby
URL:
Depends on:
Blocks:
 
Reported: 2015-09-23 11:18 CEST by Xerxes Rånby
Modified: 2015-09-27 01:41 CEST (History)
1 user (show)

See Also:
Type: ---
SCM Refs:
Workaround: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Xerxes Rånby 2015-09-23 11:18:55 CEST
On 8 sept 2015 Raspberry Pi foundation announced an 7" TFT add-on display with 10 point multi-touch for use with the Raspberry Pi
https://www.raspberrypi.org/blog/the-eagerly-awaited-raspberry-pi-display/

This new touch display sends absolute screen coordinates

NEWT BCM VC IV gets correct absolute screen coordinates when it is used in combination with the X11UnderlayTracker from inside xorg = working satisfactory

However the NEWT BCM VC IV still receive relative screen coordinates instead of absolute when used from console = not working satisfactory
The mouse pointer is placed at a different location compared to where the user puts its finger on the display.


In order to fix this issue the LinuxEventDeviceTracker need to support mouse events (best since it will add multitouch support as well)
http://jogamp.org/git/?p=jogl.git;a=blob;f=src/newt/classes/jogamp/newt/driver/linux/LinuxEventDeviceTracker.java;hb=HEAD
alternatively the current in use LinuxMouseTracker needs to be enhanced to handle absolute touch input.
http://jogamp.org/git/?p=jogl.git;a=blob;f=src/newt/classes/jogamp/newt/driver/linux/LinuxMouseTracker.java;hb=HEAD
Comment 1 Sven Gothel 2015-09-27 00:44:50 CEST
Expected behavior: All events received to a NEWT window:
  - shall be clipped to its window bounds,
    i.e. no exterior events shall be received

  - shall be relative coordinates to the window location
    on the screen. Those become absolute screen coordinates
    for fullscreen windows .. of course.