Edge Designer / Client Launcher issue with Touch Screen

Ignition
1

I’m using Ignition Edge 8.0.5 on Linux Mint 19.2 Mate Desktop. I installed Ignition from the zip file and have it running as soon as the computer boots. I have tested this against Oracle Java 8 and OpenJDK 11. With both of them when I open the Vision Client Launcher or the Designer Launcher neither one will register a click when I use the touch screen. For instance if I click on “Add Designer” from the designer launcher, then the button will turn dark like I’m clicking it, however nothing will happen. When I use a mouse it will turn dark and then open a new screen.

I am assuming this has something to do with some nuance between the exact event fired between a true mouse click and the touch screen’s mouse click, but is there anyway I can work around this?

2

Sounds like a bug in the touch driver–not delivering “mouse release” events.

3

Maybe you can use xinput -test with a mouse and then with the touch screen to see if you’re missing the release or some other events.

4

Using xinput list to find out my device information and then xinput test-xi2 10 (where xi2 referes to my slave pointer (2) and 10 is the device’s id). With a regular mouse I’ll get a RawButtonPress and RawButtonRelease event but with the touch screen I get a RawTouchBegin and a RawTouchEnd event. Here’s the full dialog for the touchscreen:

EVENT type 22 (RawTouchBegin)
   Device: 10 (10)
   detail: 10
   valuators:
      0:38067.66 (38067.66)
      1:22994.68 (2294.68)

EVENT type 24 (RawTouchEnd)
   Device: 10 (10)
   detail: 10
   valuators:
      0:38067.66 (38067.66)
      1:22994.68 (2294.68)
5

Try xev -event mouse and then click on the little test window that pops up with the mouse and again with the touch screen. The interesting output for each is probably this:

ButtonPress event, serial 25, synthetic NO, window 0x4a00001,
    root 0x6ba, subw 0x0, time 75141618, (79,87), root:(2457,142),
    state 0x0, button 1, same_screen YES

ButtonRelease event, serial 25, synthetic NO, window 0x4a00001,
    root 0x6ba, subw 0x0, time 75141714, (79,87), root:(2457,142),
    state 0x100, button 1, same_screen YES
6

Using xev -event mouse I get the following using a standard usb mouse:

ButtonPress event, serial 25, synthetic NO, window 0x1c00001,
    root 0x103, subw 0x1c00002, time 4111605, (42,48), root:(700,375),
    state 0x10, button 1, same_screen YES

EnterNotify event, serial 25, synthetic NO, window 0x1c00001,
    root 0x103, subw 0x0, time 4111605, (42,48), root:(700,375),
    mode NotifyGrab, detail NotifyInferior, same_screen YES,
    focus YES, state 272

ButtonRelease event, serial 25, synthetic NO, window 0x1c00001,
    root 0x103, subw 0x1c00002, time 4112907, (42,48), root:(700,375),
    state 0x110, button 1, same_screen YES

LeaveNotify event, serial 25, synthetic NO, window 0x1c00001,
    root 0x103, subw 0x0, time 4112907, (42,48), root:(700,375),
    mode NotifyUngrab, detail NotifyInferior, same_screen YES,
    focus YES, state 16

LeaveNotify event, serial 25, synthetic NO, window 0x1c00001,
    root 0x103, subw 0x1c00002, time 4118097, (42,48), root:(700,375),
    mode NotifyGrab, detail NotifyVirtual, same_screen YES,
    focus YES, state 24

And I get the following using a touch screen

ButtonPress event, serial 25, synthetic NO, window 0x1c00001,
    root 0x103, subw 0x1c00002, time 4190526, (42,37), root:(465,331),
    state 0x10, button 1, same_screen YES

EnterNotify event, serial 25, synthetic NO, window 0x1c00001,
    root 0x103, subw 0x0, time 4190526, (42,37), root:(465,331),
    mode NotifyGrab, detail NotifyInferior, same_screen YES,
    focus YES, state 16

MotionNotify event, serial 25, synthetic NO, window window 0x1c00001,
    root 0x103, subw 0x0, time 4190663, (42,37), root:(465,331),
   state 0x110, is_hint 0, same_screen YES

ButtonRelease event, serial 25, synthetic NO, window 0x1c00001,
    root 0x103, subw 0x1c00002, time 4190663, (42,37), root:(465,331),
    state 0x110, button 1, same_screen YES

LeaveNotify event, serial 25, synthetic NO, window 0x1c00001,
    root 0x103, subw 0x0,time 4190663, (42,37), root:(465,331),
    mode NotifyUngrab, detail NotifyInferior, same_screen YES,
    focus YES, state 16

LeaveNotify event, serial 25, synthetic NO, window 0x1c00001,
    root 0x103, subw 0x1c00002, time 4192544, (42,37), root:(465,331),
    mode NotifyGrab, detail NotifyVirtual, same_screen YES,
    focus YES, state 24
7

And if it helps, when I do xinput list, the touch screen is listed as “Renesas Electronics USB Touch (Win8)”

8

Sorry I’m out of ideas now. Not sure what’s going on.

9

yeah it’s weird. It only happens in the Designer and client launchers. I use the mouse release event all the time in my project and it has zero issues. The launchers show that they see the press by turning dark blue but then do nothing.