Closed GoogleCodeExporter closed 8 years ago
Which Swedish keyboard? The internal one works fine.
Original comment by kennytm@gmail.com
on 29 Mar 2009 at 3:37
This also happends with the Norwegian Keyboard.
Original comment by anders.s...@gmail.com
on 31 Mar 2009 at 10:38
Sorry, I still cannot reproduce the problem. I've tried the Norsk & Svenska of
the
both the all-in-one and 5-row keyboards in iPuhelin but still I can type "komm"
as
expected. (I'm on 2.2.1 with iPod Touch 1G using the iKeyEx on BigBoss right
now).
Original comment by kennytm@gmail.com
on 1 Apr 2009 at 10:16
Hmm.. I thought it maybe had something to do with biteSMS, but now i tried to
reproduce the problem in mail also, and it happens there too.. You have to be
in the
text field in messages or mail, if you try in the "send to" field, its ok.. I
have
the newest ikeyex with 5-row Norwegian keyboard from BigBoss.
Step by step to reproduse the problem.
Go to mail, and then select new (lower right corner).
Skip down to the message field and try to write Kommer or Hjemme.
For me its impossible to write the second M. If i write one M, and then hold my
thumb
down and drag it back and forth over M, the keyboard switches between L and Ø.
It's not a big problem, but its the only problem with my phone right now.
I have a Jailbreaked Iphone 8gb with 2.2.1.
Other apps installed:
biteSMS
SwirlyMMS
Bossprefs
mxTube
Cycorder
Makeitmine
Original comment by anders.s...@gmail.com
on 1 Apr 2009 at 10:26
@4: No, that's still fine with me.
Would you mind going to Settings -> iKeyEx -> Email Diagnosis Info to send me
the
detail? Also change the subject of mail to something like "Issue 78" so I won't
delete your mail. But make sure you don't change the content.
Original comment by kennytm@gmail.com
on 1 Apr 2009 at 12:04
I have now sent you two files, one with "Issue 78" subject, and one with "Issue
78
Crash reports".
I got a message saying: "There are no recent crashes related to iKeyEx. Do you
still
want to send this email?" With three options. "Cancel", "send" and "Send all
crash
reports". I have sent the two mails from the last two options.
Original comment by anders.s...@gmail.com
on 1 Apr 2009 at 12:23
@6: I've received the email. I'll try to install packages to match your config
and
see if I can reproduce the problem.
Original comment by kennytm@gmail.com
on 1 Apr 2009 at 12:48
Ok, I can reproduce it when only 1 keyboard is present.
(As a workaround, enable >1 keyboards).
Original comment by kennytm@gmail.com
on 1 Apr 2009 at 12:55
Original comment by kennytm@gmail.com
on 1 Apr 2009 at 12:58
I still have this problem when I enable >1 keyboards. I have tried to enable
both the
builtin Norwegian keyboard, the english one, and two ikeyex keyboards at the
same
time, but i stille have the problem.
Do i have to reboot or something?
Original comment by anders.s...@gmail.com
on 1 Apr 2009 at 1:21
I think I've figured out what's wrong. That's iPhoneOS's fault again.
For a quick fix, go to
/Library/iKeyEx/Keyboards/5Row<LANGUAGE>.keyboard/
then edit "layout.plist", then between
<key>Alphabet</key>
<dict>
and
<key>arrangement</key>
<array>
insert these 2 lines:
<key>usesKeyCharges</key>
<false/>
then save the file and try again. (Force quit MobileMail first if you want to
test in
Mail.)
---
The problem is a feature called "key charges". The software will compute the
probability of which key you'll press next, and "enlarge" its hitting area when
it's
high. The problem is, when I add one more row, the buttons are so cramped that
the
key's area is totally conquered by neighboring high probability keys.
I encountered this problem during development of 5-Row QWERTY, and therefore
this key
is added to explicitly disable the key charges feature.
This only affects those sublayouts that the probability can be calculated, i.e.
normal key areas. That's why the "Send to:" field acts normally. I guess the
problem
comes along with the fix of issue 31.
I hope iPuhelin (Tomi?) is reading this, so the fix can be deployed.
If this modification helps, I'll close this bug as "WontFix".
Original comment by kennytm@gmail.com
on 1 Apr 2009 at 1:39
Yes, this did the trick. Thanks alot. I assume iPhuelin releases a new keyboard
when
he has read this. Anyway, your help was much appreciated.
Original comment by anders.s...@gmail.com
on 1 Apr 2009 at 3:59
Original comment by kennytm@gmail.com
on 1 Apr 2009 at 4:13
Original issue reported on code.google.com by
hampus.p...@gmail.com
on 27 Mar 2009 at 9:02