Talk:Changing keyboard layout on Touchpad

From WebOS Internals
Jump to: navigation, search

Cursor keys

Thanks for this; one thing I very quickly realised was the most amazing omission from the TP keyboard was any way of moving the cursor (especially if you mis-type a long web address), specifically [home] [end] [->] and [<-] options. I had been wondering whether the layout itself could be amended to insert a generic cursor-move key (pref by reducing the width of the space bar and adding [<-] and [->] under the 'n' and 'm' keys, with shift giving the [home] and [end], but the info here suggests that may not be possible. Having other options on the [Tab] key might be? Anyway, anyone else looking at possible ways to add these oh-so-necessary functions? --AlisonW 12:21, 29 August 2011 (UTC)

Nope, sorry. As I get it, it is mostly not even keyboard but paste tool. All it does is pasting characters that are assigned to buttons in text. May be there are special buttons for moving cursor programmed somewhere in binary, but as they are not present in standard layouts itself I cannot say which codes they can have. Compvir 12:29, 29 August 2011 (UTC)

Keys not sending

I edited one of the layouts to create a pIqaD keyboard, and the new keyboard layout patches fine and displays correctly (except for the 5 and 6 keys which show arabic characters instead even though they display correctly elsewhere in the OS). Unfortunately none of the keys will send the new characters when tapped. The SETs still popup and work correctly thoughA copy of the layout can be found here and a screen shot is here. Any ideas as to why it won't send them? I can copy and paste the same Unicode characters from an app I made and they display correctly. --Qurgh 19:09, 29 August 2011 (UTC)

Hard to say. There can be some internal limitation. Though Klingon characters are in range of UTF-16 they are pretty close to it's end. Patched file (I've tested your json) is pertty normal. Characters are normal as should be. So The only reason I can see they are not typing should be some limit in interpretation of them by webOS. Compvir 19:36, 29 August 2011 (UTC)

Thanks for the reply. I'm able to use the characters in other apps (I have an Enyo app that converts roman characters to Unicode, which I can then copy/paste into other apps and just type) so I'm guessing this is a limitation of LunaSysMgr and not webOS in general. I guess more research is needed. Maybe I'll try asking on the HP Dev boards. --Qurgh 20:15, 29 August 2011 (UTC)