bugs on touch screen devices

[normandy8757675]

I have just installed NsCDE on tablet PCs today and I have come across these following bugs:

Root menu won't show up when tapped, on the empty desktop, with stylus (root menu shows up just fine on tablets with regular touchscreens, non-wacom digitisers)

install icon, front-panel rename function doesn't work with OnBoard as text forms requires mouse-hover.

Although, there is a workaround on regular multi-touchscreen devices: touch and hold on the textbox you want to type, this will keep the cursor hover on the textbox, and use on-screen keyboard to type in, but this is rather inconvenient (on original CDE you don't have to hover your mouse on textbox to rename workspaces). Also, it is impossible to rename workspaces on tablets with palm cancellations (mostly wacom-based digitisers) using on-screen keyboard because multi touch is disabled while the stylus tip is close to the screen. The trick mentioned earlier doesn't work as two finger tap is functioned as right-click on wacom-based touchscreens (Wacom ISD V4)

the icon menu options won't show up, when the icon is tapped with stylus. (shows up just fine when tapped with finger or left-click with USB mouse). Software have to be deiconified with the right-click button on stylus.

When using firefox (with xinput2 enabled as "env") and Anki on NsCDE, Xinput crash more often making the touch screen become unresponsive inside apps's windows, touchscreen works fine outside the window. This only happens on touch sensor and on capacitive touchscreen devices. Everything works perfectly with the built-in stylus

OS: Debian 11 Bullseye

[NsCDE]

Hi @normandy8757675

1. For a Root Menu, maybe try to tap and then move slightly. This may trigger the same action as with normal mouse.
2. This is the problem of the TextField widget of FvwmScript. Try pressing TAB until you select it. You will not notice when it is selected visually until you try to type something. I'm guessing this: it MAY work. If not, I will try to arrange something for FvwmScript in fvwm3 ...
3. For the last one, I really don't know how to proceed right now. Either someone with such devices should get a bit involved in debugging, or I should wait for opportunity to get hands on on such touch device. Currently, I don't have intention to by it.