gujjwal00 / avnc

VNC Client for Android
GNU General Public License v3.0
660 stars 59 forks source link

Feature Request - Stylus Support #263

Open leandro-benedet-garcia opened 2 weeks ago

leandro-benedet-garcia commented 2 weeks ago

Hello, I have a Samsung S6 2024 that has a stylus support and I am using AVNC client side and the command

krfb-virtualmonitor --name WirelessDisplay --resolution 2000x1200 --password 123456 --port 5900

To generate a virtual screen and open a vnc server in my machine with a KDE 6 session running wayland. The mouse does move when I hover my pen, but when I press my stylus to the screen, nothing happens.

So I would like to request the feature of stylus support, preferably with pressure support so I can sculpt in Blender in my computer.

I would be able to implement this feature if someone would be able to guide me which files to modify

gujjwal00 commented 2 weeks ago

AVNC already has support for stylus, so this may be a bug. Can you please go to AVNC Settings => Tools => Touch test, record couple of gestures with stylus, and post the logs here?

preferably with pressure support so I can sculpt in Blender in my computer.

VNC protocol doesn't have any concept of pressure, or even a stylus for that matter. So this is not possible.

I would be able to implement this feature if someone would be able to guide me which files to modify

This is the main file which handles touch events. If you have Android Studio set up, you can debug AVNC to see why click is not working.

leandro-benedet-garcia commented 2 weeks ago

Here are the logs: https://pastebin.com/4ZLZmHNN

Also, I tested again, the mouse does not move in the computer, I am starting to think it might be a bug in krfb-virtualmonitor instead.

VNC protocol doesn't have any concept of pressure, or even a stylus for that matter. So this is not possible.

Strange, TurboVNC seems to support them (Why I asked in the first place, thought vnc protocol supported it)

Do they have a extra implementation of the vnc protocol?

gujjwal00 commented 2 weeks ago

The logs look normal, so this might be a server issue. Please try with a different VNC server. Or try a different VNC client, e.g. MultiVNC, to rule out issue in AVNC.

Do they have a extra implementation of the vnc protocol?

Yes, TurboVNC is probably using an extension.