Hi Valentin,
One thing that will work for sure (as a workaround) is if you switch to "Single-handed input mode" and long-tap. That mode will present you with a graphical representation of a mouse for you to select the type of click you'd like for it to perform.
I looked at the log and it's actually quite helpful. I see a puzzling thing that you may help explain:
I see ACTION_BUTTON_PRESSes with both TOOL_TYPE_MOUSE and TOOL_TYPE_FINGER a few seconds apart. Do you think those are you clicking and tapping with two fingers respectively?
05-01 15:30:43.901 30859 30859 D RmtClientsInputListener:
onGenericMotionEvent, event: MotionEvent { action=ACTION_BUTTON_PRESS,
actionButton=BUTTON_SECONDARY, id[0]=0, x[0]=1194.5508, y[0]=1037.9453,
toolType[0]=TOOL_TYPE_FINGER, buttonState=BUTTON_SECONDARY,
classification=NONE, metaState=0, flags=0x100040, edgeFlags=0x0,
pointerCount=1, historySize=0, eventTime=4107023, downTime=4106530,
deviceId=10, source=0x2002, displayId=0, eventId=473747550 }
and
05-01 15:30:46.502 30859 30859 D RmtClientsInputListener: onGenericMotionEvent, event: MotionEvent { action=ACTION_BUTTON_PRESS, actionButton=BUTTON_SECONDARY, id[0]=0, x[0]=1110.582, y[0]=855.43164, toolType[0]=TOOL_TYPE_MOUSE, buttonState=BUTTON_PRIMARY|BUTTON_SECONDARY, classification=NONE, metaState=0, flags=0x100000, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=4109623, downTime=4109133, deviceId=10, source=0x2002, displayId=0, eventId=188030639 }
Looking at the input code, it definitely seems like the application lacks support for MotionEvent with action=ACTION_BUTTON_PRESS in any case. Would you kindly open a feature request at
https://github.com/iiordanov/remote-desktop-clients/issues, and I'll try implementing support that you can test in Beta.
Thanks again!
iordan