ideas

asked 2013-12-24 22:32:14 +0300

parasemic

975 ●9 ●15 ●17

updated 2014-03-20 20:07:18 +0300

Alex

10635 ●181 ●247 ●252

I'll just list a couple of problems, bugs and ideas about the keyboard. I'll add to the main text if you have other ideas etc.

Bugs:

The haptic responses seem inaccurate, and the force of haptics jumps between hard and really soft.
The keyboard doesn't go back to the upper case mode after a dot and a space, except in messages app.
The "confirming letter", or the bigger letter appearing on top of your finger while tapping, seems to not show every time on the letters next to the edge of the screen. eg. Q A Å Ä etc. This seems to happen when tapping the edge of the screen.
(added on 20th March 2014) There is some annoying bug while coppying some text in e.g. messageing and notes app. (see my comment)

Other stuff to discuss:

[parasemic]

Correct me if I'm wrong, but there doesn't seem to be a way to turn off word prediction.
The space button is too thin and the dot is too wide, and I keep on pressing dot instead of the space. It.is.very.annoying.

[Ozymandias]

The predictions automatically create a space after a word. I would like this to be optional, as I have to use backspace if I want to place a period. (I know that way I would have to press space more, but that feels more natural than using backspace, it breaks my flow of writing.)
Edit by jgr: After tapping the prediction word, just tap the sentence mark (comma, dot etc.) – the space will be removed automatically.
Allow for more than one language for the predictions. I usually write half in German and half in English (within one and the same message).

[ortylp]

Word prediction: use probability of next word based on previously entered text, it dramatically speeds up writing of chat messages

[andreibechet]

Double tap on the space key should create a dot.

edit retag flag offensive close delete

Comments

I second that fourth point of yours.

jaine ( 2013-12-24 22:34:55 +0300 )edit

Only fourth? :D

parasemic ( 2013-12-24 22:42:37 +0300 )edit

Fourth point if truth only in Web browser. In native apps I may edit everywhere on input line with nice magnify.

Kaacz ( 2013-12-24 23:18:33 +0300 )edit

I think it's present elsewhere too, but I'll investigate. Mind voting up so this won't get buried?

parasemic ( 2013-12-24 23:27:07 +0300 )edit

2

Two additions of mine:

the predictions automatically create a space after a word. I would like this to be optional, as I have to use backspace if I want to place a period. (I know that way I would have to press space more, but that feels more natural than using backspace, it breaks my flow of writing.)
Allow for more than one language for the predictions. I usually write half in German and half in English.

Ozymandias ( 2013-12-24 23:29:21 +0300 )edit

1

answered 2013-12-27 22:41:04 +0300

parasemic

975 ●9 ●15 ●17

updated 2013-12-27 22:42:09 +0300

"When trying to correct word written earlier, while the text prediction is on (line under the current word), you can't change the place you're typing to. It seems like it does, but it keeps on writing after the last word."

This was fixed in 1.0.2.5 update.

edit flag offensive delete publish link

1

answered 2014-02-24 08:18:55 +0300

zlatko

16489 ●109 ●150 ●142

In landscape mode all row are shrunk in vertical direction to cope with the decreased height of the screen. In this situation space bar row is quite "thin" both visually and as a touch area. It will be good if it is made slightly higher. Especially as space bar is currently used for changing keyboard layouts.

edit flag offensive delete publish link

1

answered 2014-03-04 17:33:25 +0300

ejjoman

3739 ●48 ●67 ●75

https://github.com/ejjoma...

The word after a colon should be written capitalized. At least in German, the colon is treated like a period and the following sentence has to start with a capitalized letter.

edit flag offensive delete publish link

1

answered 2014-03-06 16:20:40 +0300

Vivien

2027 ●38 ●54 ●58

When typing a closing bracket, the preceding space should be removed (like for comma, dot, ...)

edit flag offensive delete publish link

0

answered 2014-03-20 19:54:02 +0300

Alex

10635 ●181 ●247 ●252

I want to add this:

There is some annoying bug by copying some text in e.g messageing and notes app:

There is no problem if you mark some text and grab one of the dots to mark some more text while moving the (first) dot to the top but if you move the (second) dot at the top first (after you already marked some larger text) AND then move the dot to the bottom you will be unable to see what text you are marking at the moment AND the text is also not moving to the top so you are unable to mark all the text you want.

This should be fixed quickly because this is really a annoying bug.

edit flag offensive delete publish link

0

answered 2014-04-17 17:54:57 +0300

tortoisedoc

11414 ●172 ●269 ●287

http://kastlunger.blogspo...

exchange web access does not alloe scrolling when kb is displayed. particularly difficult in landscape.

edit flag offensive delete publish link

0

answered 2014-04-18 12:30:20 +0300

rod
1150 ●21 ●33 ●34

I have suggested this already in a separate thread: I would like to have the keyboard available in any application e.g. via a global gesture (someone suggested a two finger swipe). This could allow for easy filtering or searching in many for example in the calendar or in the contacts. Imho this would be a nice replacement for a real hardware keyboard. Not as comfortable but at least available everywhere.

edit flag offensive delete publish link

Keyboard bugs/changes/ideas

Comments

17 Answers

Question tools

Stats

Related questions

Keyboard bugs/changes/ideas

Comments

17 Answers

Question tools

Public thread

Stats

Related questions