Sample Header Ad - 728x90

Touch screen behaviour

0 votes
0 answers
21 views
I want to develop a simple GUI panel using Raspberry Pi 4 and Touchscreen LCD module. My desktop is LXDE and below is the uname output. Linux rpi4 6.6.51+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt3 (2024-10-08) aarch64 GNU/Linux I will have only website shortcuts and possibly VLC on the desktop. What I can't figure out is how to emulate similar behavior as Android. I want to be able to open shortcuts with single tap on the icon as well as scroll the page in the browser using tap and swipe. Right now I need to double tap on the screen to open shortcuts. Trying to scroll in the browser window just selects the text in both Chromium and Firefox. Below is evtest output. How needs to be adjusted in the config files to achieve what I want? Input driver version is 1.0.1 Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x0 Input device name: "10-0038 generic ft5x06 (17)" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 330 (BTN_TOUCH) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 648 Min 0 Max 799 Event code 1 (ABS_Y) Value 281 Min 0 Max 479 Event code 47 (ABS_MT_SLOT) Value 0 Min 0 Max 9 Event code 53 (ABS_MT_POSITION_X) Value 0 Min 0 Max 799 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min 0 Max 479 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min 0 Max 65535 Properties: Property type 1 (INPUT_PROP_DIRECT) Testing ... (interrupt to exit) Event: time 1738696220.941421, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 105 Event: time 1738696220.941421, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 431 Event: time 1738696220.941421, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 229 Event: time 1738696220.941421, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 Event: time 1738696220.941421, type 3 (EV_ABS), code 0 (ABS_X), value 431 Event: time 1738696220.941421, type 3 (EV_ABS), code 1 (ABS_Y), value 229 Event: time 1738696220.941421, -------------- SYN_REPORT ------------ Event: time 1738696220.966967, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 432 Event: time 1738696220.966967, type 3 (EV_ABS), code 0 (ABS_X), value 432 Event: time 1738696220.966967, -------------- SYN_REPORT ------------ Event: time 1738696221.037503, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 434 Event: time 1738696221.037503, type 3 (EV_ABS), code 0 (ABS_X), value 434 Event: time 1738696221.037503, -------------- SYN_REPORT ------------ Event: time 1738696221.061450, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 435 Event: time 1738696221.061450, type 3 (EV_ABS), code 0 (ABS_X), value 435 Event: time 1738696221.061450, -------------- SYN_REPORT ------------ Event: time 1738696221.085531, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 228 Event: time 1738696221.085531, type 3 (EV_ABS), code 1 (ABS_Y), value 228 Event: time 1738696221.085531, -------------- SYN_REPORT ------------ Event: time 1738696221.109497, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 436 Event: time 1738696221.109497, type 3 (EV_ABS), code 0 (ABS_X), value 436 Event: time 1738696221.109497, -------------- SYN_REPORT ------------ Event: time 1738696221.133561, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 438 Event: time 1738696221.133561, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 227 Event: time 1738696221.133561, type 3 (EV_ABS), code 0 (ABS_X), value 438 Event: time 1738696221.133561, type 3 (EV_ABS), code 1 (ABS_Y), value 227
Asked by Farid83 (111 rep)
Feb 4, 2025, 07:13 PM