Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] jtx input fields don't accept characters via a VNC connection #1539

Open
git-3847 opened this issue Aug 11, 2024 · 1 comment
Open
Assignees
Labels
bug Something isn't working

Comments

@git-3847
Copy link

Describe the bug
I have a VNC server on my phone (droidVNC-NG), this makes it much easier to do lots of tasks at my finger friendly notebook or desktop keyboard. I recently installed jtxBoard (and like it a lot, with a few reservations), but its the first Android app I've encountered where I couldn't use VNC keyboard input. I have to use the soft keyboard on the device (either through VNC mouse events or true screen events).

To Reproduce

  1. Install droidVNC-NG
  2. Connect to the phone with a standard vnc client (I use FreeBSD vncviewer)
  3. Test keyboard input with other apps (Email client, calendar, text editor)
  4. Test keyboard input on jtxBoard (and hopefully reproduce this issue!)

Expected behavior

  1. It would be awesome if the VNC generated keystrokes got to the jtx input field

Screenshots
Not applicable

Device and version

  • Teracube_2e_A11_05
  • Android 11
  • jtx Board version: 2.09.00.gplay
  • Downloaded from: Google Play (and gleefully paid up)
@git-3847 git-3847 added the bug Something isn't working label Aug 11, 2024
@patrickunterwegs
Copy link
Member

Hi @git-3847 , thanks for your feedback and issue report!
I will have a bit of a closer look at this, but it's very likely that this is related to the UI framework. jtx Board is using Jetpack Compose, which is the newest UI framework by Google. Older apps are likely to still use XML layouts.
From the UI framework the apps uses default textboxes, the customization that is done is only applied via the default customization options, so there's no custom implementation on any textfield.

So even if I have a detailed look now, it's very unlikely that I would find a switch or so that would just solve the problem. I mean, why shouldn't that switch be on in the first place then.
I'll try it out, but I believe it would rather be an issue in droidVNC-NG, that doesn't properly forward the information to textfields based on Jetpack Compose. Or it's a problem of the UI component itself (I also wouldn't be surprised about that because there are also some other edge-case issues in other use cases).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants