Editing Documentation/Maemo 5 Developer Guide/Porting Software/Adapting UI Inputs
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 8: | Line 8: | ||
Some important things to remember: | Some important things to remember: | ||
| - | * The '''Enter''' key on the N900 sends the | + | * The '''Enter''' key on the N900 sends the ''KP_ENTER'' signal, not the ''ENTER'' signal. |
* Numbers have to be entered using the '''Fn''' key modifier: they don't work well (or at all) as control keys. Depending on how text input is read, they may also not work for text input. | * Numbers have to be entered using the '''Fn''' key modifier: they don't work well (or at all) as control keys. Depending on how text input is read, they may also not work for text input. | ||
* The keyboard layout is locale-specific. ''You cannot rely on any keys being in a given place, or even existing at all, on every N900!'' | * The keyboard layout is locale-specific. ''You cannot rely on any keys being in a given place, or even existing at all, on every N900!'' | ||
| Line 22: | Line 22: | ||
===Solution 2: The QWERTY Switch=== | ===Solution 2: The QWERTY Switch=== | ||
| - | Another approach that may be appropriate for apps that require very little or no text input (because the user is going to expect the keys to enter the same text as always) is to change the locale of the user's keyboard for the duration of program execution. Special care should be taken to not create side-effects if this is done. In particular, be sure to | + | Another approach that may be appropriate for apps that require very little or no text input (because the user is going to expect the keys to enter the same text as always) is to change the locale of the user's keyboard for the duration of program execution. Special care should be taken to not create side-effects if this is done. In particular, be sure to |
| - | + | ||
# Restore the user's original layout on exit | # Restore the user's original layout on exit | ||
# Restore the user's original layout when they switch away from the app | # Restore the user's original layout when they switch away from the app | ||
| Line 33: | Line 32: | ||
'''N.b.''' This doesn't restore properly custom user layouts set with setxkbmap, and might be improved by using that utility. Please update this portion of the wiki if you adapt this method to work properly with custom user layouts. | '''N.b.''' This doesn't restore properly custom user layouts set with setxkbmap, and might be improved by using that utility. Please update this portion of the wiki if you adapt this method to work properly with custom user layouts. | ||
| - | + | Maemo-specific patch to work around the Nokia design flaw that left large portions of Europe without up and down arrow keys. | |
| - | Maemo-specific patch to work around the Nokia design flaw that left large portions of Europe without up and down arrow keys. | + | -- Flandry <davidfalkayn@gmail.com> 20100114 |
| - | -- Flandry <davidfalkayn@gmail.com> 20100114 | + | --- src/uqm.c 2009-11-07 09:23:35.624611920 -0500 |
| - | --- src/uqm.c 2009-11-07 09:23:35.624611920 -0500 | + | +++ src/uqm.c 2010-01-14 22:12:54.972781312 -0500 |
| - | +++ src/uqm.c 2010-01-14 22:12:54.972781312 -0500 | + | TFB_InitInput (TFB_INPUTDRIVER_SDL, 0); |
| - | + | // Program initiation completed successfully | |
| - | + | + // MAEMO: Save the user's native keyboard layout and switch to known arrow-key compliant one | |
| - | + // MAEMO: Save the user's native keyboard layout and switch to known arrow-key compliant one | + | + system("/usr/bin/gconftool-2 -g /apps/osso/inputmethod/int_kb_layout > /home/user/.uqm/int_kb_layout"); |
| - | + system("/usr/bin/gconftool-2 -g /apps/osso/inputmethod/int_kb_layout > /home/user/.uqm/int_kb_layout"); | + | + system("/usr/bin/gconftool-2 -s /apps/osso/inputmethod/int_kb_layout us -t string"); |
| - | + system("/usr/bin/gconftool-2 -s /apps/osso/inputmethod/int_kb_layout us -t string"); | + | // Start main loop |
| - | + | StartThread (Starcon2Main, NULL, 1024, "Starcon2Main"); | |
| - | + | ||
| - | + | ||
This makes two system calls to gconftool-2. The first saves the user's current layout into a file in the app configuration directory. (Be sure to create the user's app configuration directory before this call!) Instead of saving the original value to a file, you might use a different C system call function to enable storing the value in a variable, or read the value directly. The important part is to store initial state. | This makes two system calls to gconftool-2. The first saves the user's current layout into a file in the app configuration directory. (Be sure to create the user's app configuration directory before this call!) Instead of saving the original value to a file, you might use a different C system call function to enable storing the value in a variable, or read the value directly. The important part is to store initial state. | ||
| - | + | ||
| - | + | @@ -471,6 +478,11 @@ | |
| - | @@ -471,6 +478,11 @@ | + | mem_uninit (); |
| - | + | } // End program | |
| - | + | + // MAEMO: Reset the user's keyboard layout based on the value recorded at the start | |
| - | + // MAEMO: Reset the user's keyboard layout based on the value recorded at the start | + | + system("/usr/bin/gconftool-2 -s /apps/osso/inputmethod/int_kb_layout $(cat /home/user/.uqm/int_kb_layout) -t string"); |
| - | + system("/usr/bin/gconftool-2 -s /apps/osso/inputmethod/int_kb_layout $(cat /home/user/.uqm/int_kb_layout) -t string"); | + | |
| - | + | ||
This undoes the switch with an additional system call to gconftool-2 that uses the value stored at the beginning. | This undoes the switch with an additional system call to gconftool-2 that uses the value stored at the beginning. | ||
| - | + | --- src/libs/graphics/sdl/sdl_common.c 2009-11-07 10:23:58.974265870 -0500 | |
| - | --- src/libs/graphics/sdl/sdl_common.c 2009-11-07 10:23:58.974265870 -0500 | + | +++ src/libs/graphics/sdl/sdl_common.c 2010-01-14 22:13:36.531416322 -0500 |
| - | +++ src/libs/graphics/sdl/sdl_common.c 2010-01-14 22:13:36.531416322 -0500 | + | if (Event.active.state & SDL_APPINPUTFOCUS) { |
| - | + | GameActive = Event.active.gain; | |
| - | + | + // Switch to english or user's native keyboard layout when gaining/loosing focus | |
| - | + // Switch to english or user's native keyboard layout when gaining/loosing focus | + | + if (!GameActive) |
| - | + if (!GameActive) | + | + system("/usr/bin/gconftool-2 -s /apps/osso/inputmethod/int_kb_layout $(cat /home/user/.uqm/int_kb_layout) -t string"); |
| - | + system("/usr/bin/gconftool-2 -s /apps/osso/inputmethod/int_kb_layout $(cat /home/user/.uqm/int_kb_layout) -t string"); | + | + else |
| - | + else | + | + system("/usr/bin/gconftool-2 -s /apps/osso/inputmethod/int_kb_layout us -t string"); |
| - | + system("/usr/bin/gconftool-2 -s /apps/osso/inputmethod/int_kb_layout us -t string"); | + | } |
| - | + | ||
| - | + | ||
| - | The | + | The SDL_APPINPUTFOCUS active state changes when an SDL app window is pushed to a thumbnail by the task switcher. When that event is detected, the user's original keyboard layout is restored, and then the qwerty (''us'') layout is restored when the app regains focus. |
==Documenting the UI== | ==Documenting the UI== | ||
Learn more about Contributing to the wiki.