isontheline / pro.webssh.net

iOS / iPadOS / macOS SSH Client
https://apps.apple.com/us/app/id497714887
MIT License
316 stars 46 forks source link

Hardware mouse without physical keyboard problem #1026

Closed isontheline closed 10 months ago

isontheline commented 10 months ago

Bug description

Happy new year!🎆

Thanks for your work on webssh app so far, I'm very grateful for your hard work.

I now have a small inconvenience bug to report. It hasn't to do with using only bluetooth mouse (without bluetooth keyboard) while using ios app. In this instance the onscreen keyboard still hides automatically (to minimal mode/only some function keys are available), although I only have hardware mouse connected without physical keyboard.

See screenshot that I`ve attached below.👇🏾

image

The other apps, for example Notes app does something similar but I can touch on language button to show keyboard and from then on the onscreen keyboard persists, thereby I can continue working fine.

With webssh I didn't find a way to still bring up onscreen keyboard in full size.

Again screenshot from Notes

image

image

I tried Termius and the onscreen keyboard automatically closes after connecting the bluetooth mouse. There is also no possibility (or at least I didn't find one) to show onscreen keyboard as in Notes app for example.

isontheline commented 10 months ago

Could you try this please ?

https://support.logi.com/hc/en-us/articles/5303593287063-Set-up-and-use-a-Logitech-mouse-on-iPad-OS

Using the on-screen keyboard Most of our mice have advanced buttons that are recognized by the system as keyboard shortcuts. Due to this, when a mouse is connected, the system believes that an external keyboard is also connected and the on-screen keyboard will disappear.

If you don’t use an external keyboard and want to keep using the on-screen keyboard, make sure that Show Onscreen Keyboard is enabled.

image

isontheline commented 10 months ago

It worked after turning on assistive touch switch along with the Show onscreen keyboard switch. This looks like a possible solution until or if somewhere in the future iOS gets a fix ;) Thanks and have a nice day!