11-16-2013, 09:21 PM | #181 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
Where kTerm is the only one that is over-riding your system locale settings during the startup. Give it another try without your native locale settings (I.E: either change the system defaults, or over-ride them during the start-up of whatever your testing with environment settings). |
|
11-17-2013, 06:25 AM | #182 | |
Developer's Corner Mascot
Posts: 486
Karma: 1277790
Join Date: Sep 2013
Device: Kindle Paperwhite 5.3.4, Kindle Keyboard 3.4
|
Quote:
I wonder what other does change on kterm only mmh... |
|
Advert | |
|
11-17-2013, 06:34 AM | #183 |
Developer's Corner Mascot
Posts: 486
Karma: 1277790
Join Date: Sep 2013
Device: Kindle Paperwhite 5.3.4, Kindle Keyboard 3.4
|
Don't know if it helps, but not working chars are:
capital C capital F capital J capital X All the rest seems to work What do these letters have in common? Last edited by Aeris; 11-17-2013 at 06:36 AM. |
11-17-2013, 10:19 AM | #184 |
but forgot what it's like
Posts: 741
Karma: 2345678
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
|
|
11-17-2013, 10:21 AM | #185 |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
perhaps Not intercepted by some other process?
Unsure. |
Advert | |
|
11-17-2013, 10:45 AM | #186 | |
Developer's Corner Mascot
Posts: 486
Karma: 1277790
Join Date: Sep 2013
Device: Kindle Paperwhite 5.3.4, Kindle Keyboard 3.4
|
Dunno... weird mistery...
The same problem occurs with xdotool. And can be even better spotted if you are using a Custom Dialog. See in the screenshot below the result of the command: Quote:
EDIT: here there is that special char: £ Last edited by Aeris; 11-17-2013 at 03:34 PM. |
|
11-17-2013, 11:22 AM | #187 |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
right yeah.
This is known behaviour. I am trying to remember what was done to fix this last time. Spoiler:
*scratches head* I believe one needs to actually post the keystroke event or something... Hmm. err.. ah yeah: https://www.mobileread.com/forums/sho...3&postcount=26 It is quite a peculiar setup I know... but I think that answer lies in this direction... |
11-17-2013, 12:51 PM | #188 |
Developer's Corner Mascot
Posts: 486
Karma: 1277790
Join Date: Sep 2013
Device: Kindle Paperwhite 5.3.4, Kindle Keyboard 3.4
|
mmh interesting link, but... Kindle PW doesn't really seems to have these methods
Code:
lipc-set-prop -i -- com.lab126.framework insertKeystroke 100 com.lab126.framework failed to set value for property insertKeystroke (0x3 lipcErrNoSuchSource) |
11-17-2013, 01:07 PM | #189 | |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
pressing the letter j
Quote:
|
|
11-17-2013, 01:24 PM | #190 |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
This reminds me of https://www.mobileread.com/forums/sho...&postcount=115
and digging through libkb.so I note x11_send_key so... Let me dig up xsendkeys and I'll see what I get. |
11-17-2013, 02:45 PM | #191 |
Developer's Corner Mascot
Posts: 486
Karma: 1277790
Join Date: Sep 2013
Device: Kindle Paperwhite 5.3.4, Kindle Keyboard 3.4
|
Thank you Twobob, kind as usual
|
11-17-2013, 06:42 PM | #192 |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
okay. doing some digging. anything above 255 seems to just "wrap-around".
(which makes sense) CAPS LOCK is 66. (it would seem) Here's what I was testing with all the codes marked here CLOSE the keyboard in some way. The others either make no chars, are control codes, or a printable char. export MOD=255; while [ ! "${MOD}" = "8" ]; do export MOD=`expr ${MOD} - 1`; if [ ! "${MOD}" = "66" ] && [ ! "${MOD}" = "110" ] && [ ! "${MOD}" = "36" ] && [ ! "${MOD}" = "78" ] && [ ! "${MOD}" = "70" ] && [ ! "${MOD}" = "69" ] && [ ! "${MOD}" = "68" ] && [ ! "${MOD}" = "67" ] && [ ! "${MOD}" = "110" ] && [ ! "${MOD}" = "104" ] then eips "${MOD} ."; usleep 90000; echo ${MOD}; xsendkeycode $MOD 1; xsendkeycode $MOD 0; fi; usleep 90000; do ne; So 66 is Caps Lock (I believe) 110, 36, 78, 70, 69, 68, 67, 104 are other keyboard-closing key codes There is no "upper and lower" register set. Will have to figure out what maps to what at some point. did most of em. No single character code generates the "Double characters" you are experiencing, thus it has to be the "Shift"code we are passing is wrong. Bit more derping should probably nail it. There are many more in the upper registers that I missed like YEN ¥ Pound £ and _ & ^ | et cetera... Interestingly: RIGHT SHIFT maps to the weird 90 degrees pipe character and left maps to £ which explains the symbols preceding your keystrokes. Far as I can make out uppercase expects a Caps Lock 66 then the key on/off then the release. As opposed to a standard shift. I know very little about this stuff but hope all this work helps someone who DOES know what they are talking about a bit of time. I think mapping the leftover CTRL keys is probably a worthwhile exercise, for someone. I'm way bored of this now. Last edited by twobob; 11-18-2013 at 07:16 AM. |
11-17-2013, 07:29 PM | #193 | |
Developer's Corner Mascot
Posts: 486
Karma: 1277790
Join Date: Sep 2013
Device: Kindle Paperwhite 5.3.4, Kindle Keyboard 3.4
|
Quote:
Double char anyway is only in my html apps... in Midori, leafpad etc. there should be only the four-letters problem. And in kterm no issue at all... I'm afraid I should bother baf again xD P.S. I'm not sure what is your code about... must I run it or it was a test? |
|
11-17-2013, 08:21 PM | #194 | |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Tır
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
Quote:
I don't think the four keys are a mystery, I think that their key codes are being intercepted by something, possibly the Window manager. and you cant run that test without the relevant bins and libs. which I had lying around Last edited by twobob; 11-17-2013 at 08:43 PM. |
|
11-18-2013, 04:02 AM | #195 | |
Evangelist
Posts: 404
Karma: 2200000
Join Date: May 2012
Device: kt
|
Quote:
Code:
-- {{{ Key bindings globalkeys = awful.util.table.join( awful.key({ "Shift", }, "j", print_dbg_info), awful.key({ "Shift", }, "f", dumpFocusInfo), awful.key({ "Shift", }, "c", function() log("shift c down") end, chrome_raise), awful.key({ "Shift", }, "x", function() log("shift x down") end, chrome_lower), awful.key({ "Any", }, "Home", handleHomeKeyDown, handleHomeKeyUp), awful.key({ "Any", }, "Scroll_Lock", nil, screenshot), awful.key({ }, "F1", nil, accelerometerPortraitUp), awful.key({ }, "F2", nil, accelerometerPortraitDown), awful.key({ }, "F3", nil, accelerometerLandscapeLeft), awful.key({ }, "F4", nil, accelerometerLandscapeRight) ) -- }}} |
|
Tags |
browser, extensions, kindle, kual, launcher add-ons, midori |
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
release candidate 0.2-rc6 | lunohod | OpenInkpot | 0 | 12-04-2009 05:24 PM |
release candidate 0.2-rc5 | dottedmag | OpenInkpot | 50 | 12-04-2009 04:44 AM |
release candidate 0.2-rc4 | dottedmag | OpenInkpot | 10 | 11-12-2009 12:35 PM |
release candidate 0.2-rc3 | dottedmag | OpenInkpot | 10 | 11-05-2009 02:18 AM |
release candidate 0.2-rc1 | dottedmag | OpenInkpot | 36 | 10-18-2009 12:07 AM |