Opened 12 years ago

Closed 12 years ago

#215 closed enhancement/feature request (fixed)

Screen typing with touchscreen

Reported by: anonymous Owned by: cp15
Priority: critical Milestone:
Component: core Version: git master
Severity: Keywords:
Cc:

Description

since i am using navit on a touchscreen (without a keyboard) and it says on the homepage "for touchscreen usage" i think it is time for an integrated option to type in navigation targets via the screen instead of the keyboard.

to shorten input time this could be done by in incremental search (while typing).

Change History (11)

comment:1 Changed 12 years ago by KaZeR

It's done this way in the internal gui and cegui. Only the gtk relies on an external (xkbd) keyboard emulation. Does it answer your question?

comment:2 Changed 12 years ago by anonymous

so i have to start xkbd manually?

comment:3 Changed 12 years ago by KaZeR

xkbd should be started automatically when you launch the destination menu in the gtk gui. Isn't it the case?

comment:4 Changed 12 years ago by anonymous

well as no other menu than the dest menu opens up i guess it isnt :/

comment:5 Changed 12 years ago by KaZeR

Do you have it installed? Can you launch it from a term?

comment:6 Changed 12 years ago by anonymous

i dont think that there is an xkbd in ubuntu stables packet system. guess the command is hardcoded?

got an xvkbd though ..

comment:7 Changed 12 years ago by KaZeR

indeed, it's hardcoded. If you want to try before : have a look in navit/gui/gtk/destination.c and look for gtk_socket_steal(GTK_SOCKET(keyboard), spawn_xkbd("xkbd","-geometry 200x100"));

If xvkbd fits your needs this way, we'll add a config option to xml.

comment:8 Changed 12 years ago by anonymous

i tried with xvkbd but the spawn call seems to be blocking?! at least i was not able to enter any destinations before the screen keyboard window was closed.

comment:9 Changed 12 years ago by anonymous

Can you try by adding a & at the xvkbd command?

comment:10 Changed 12 years ago by anonymous

as far as i understand the code the screen keyboard process is already being forked

comment:11 Changed 12 years ago by KaZeR

  • Resolution set to fixed
  • Status changed from new to closed

now there is an internal keyboard on internal gui, and you can disable it and use the system's virtual keyboard instead by adding 'keyboard=0' to you gui definition in navit.xml

Note: See TracTickets for help on using tickets.