#463 closed enhancement/feature request (invalid)
internal gui: keyboard should be qwerty
| Reported by: | arne.anka | Owned by: | cp15 |
|---|---|---|---|
| Priority: | trivial | Milestone: | |
| Component: | gui/internal | Version: | git master |
| Severity: | Keywords: | ||
| Cc: |
Description
imo the internal gui's keyboard should be at least qwerty, not simply a-z. i append a small patch. btw: toggling between upper case and lower case seems pretty much an overkill, upper _or_ lower case should be sufficient (every special char/umlaut exists in bose cases, even the stupid german sz ligature "ß").
Attachments (1)
Change History (4)
Changed 11 years ago by arne.anka
comment:1 Changed 10 years ago by mvglasow
if that gets implemented, please make it configurable. A qwerty keyboard requires more characters in one row than the abcd one, which may become a problem when operating a QVGA-portrait device with bare fingers.
comment:2 Changed 10 years ago by kazer
- Resolution set to invalid
- Status changed from new to closed
I don't see the benefit of a qwerty keyboard here. The case is mostly useful for bookmarks naming.
About 'ss' : related to #427
I'm closing the ticket (because i'm not convinced about the use of qwerty) but feel free to reopen (and argument ;) )
comment:3 Changed 9 years ago by aaaapublic
I feel a qwerty keyboard is better. Most people are already familiar with qwerty keyboards, esp with the rise of tweeter and text messaging on qwerty soft-keyboards. it takes me far longer to type even a city name on a ABC keyboard than on a qwerty one. This would not be so bad if Navit supports the use of the device's soft-keyboard, but Navit is pretty bad in this area as well.
created against svn 2490