IPadOS and use with BT as a keyboard

Using the keyboard overlay and iPadOS… when I connect over Bluetooth, the only way I’m able to get keystrokes from the Sensel into an app is to have the on screen keyboard up. That doesn’t seem right…, am I “holding it wrong”, as Steve Jobs would say? :slight_smile:

Great to see a good product from a local company. I live in Boulder Creek, CA.

I was just considering purchasing the keyboard overlay, but if the on screen keyboard has to be present, that would be a deal breaker for me! one thing to consider, at least to make your situation better for now, pinch the keyboard down to tiny size, then you can move it around on the screen. I have my on screen ipad keyboard set this way so I can use the swipe text entry.

Oh! That’s a great idea. I’ll try that.

it’s the same with a USB C hub.

It appears that the Morph (with keyboard layout) is not recognised by iPadOS as keyboard HID (Human Input Device). On PC it works, and I guess on Mac and Linux too. Maybe it’s just an iPadOS glitch that will be resolved in an update.

Yes, for any iOS or iPadOS device, the on-screen keyboard will appear and need to be kept on screen when you’re using the Computer Keyboard Overlay.

This is because there’s no way for the Morph to specifically communicate to the iPad/iPhone which overlay you’re using. So, if you switch from the Computer Keyboard Overlay to to the Music Production Overlay, for example, then it would be a problem if your iPad/iPhone still registered the Morph as a keyboard and disabled the on-screen keyboard.

I don’t suppose the iDevice needs to know which overlay you’re using, but couldn’t the morph switch itself into a keyboard mode whenever it recognizes the keyboard overlay is in use, then communicating to the iDevice that it is a keyboard and not something else? even if you had to power cycle the morph for that to work, it would be worth it IMO.

I think the main problem would be, that the ios cannot know which overlay is active. It decides at the moment you connect. If you’d take away that overlay to use a different one, it would not deliver the onscreen keyboard when you’d need it.
One way to deal with it could be, to determine the behavior at the moment of connection. If the keyboard is there, you would never get the onscreen keyboard, even if you switched the overlay while being connected, if not you’d always get it.
This maybe could also be an option which could be switched on/off in the Sensel app…

this seems like a good solution.

Twitter RSS Facebook