[MeeGo-touch-dev] Any way t o force virtual keyboard to be used?
tomas.junnonen at nokia.com
Wed Aug 4 06:24:34 PDT 2010
On 08/04/2010 03:26 PM, ext Shane Bryan wrote:
> On Wed, Aug 04, 2010 at 01:46:23PM +0800, danny wrote:
>> In meego-handset-sdk, I use the following to see the VKB.
>> not run startmeego
>> 1) # meego-im-uiserver&
>> 2) # sms
>> or# meego-handset-people
>> or# ...
>> After set the compositing-manager to true for metacity or change to
>> compiz, I could see the VKB normally.
>> Hope useful for you.
> No it is not.
> If you recall from my initial question, I am building/testing on an
> actual netbook with the actual meego handset image installed. No SDK.
> There is not emulator or qemu in this case, nor is there metacity, just
> plain old default meego drivers, compositor, etc...
> meego-im-uiserver is running, but *no* apps will get the VKB if there is
> a "real" HKB attached.
> So if running in the emulator can get the VKB to run, again I ask (to the
> MTF devs please), what is the meegotouch-inputmethod* subsystem using to
> determine if VKB should be available so I can set/tweak/fake that in my
> development system?
The state is read from the "/maemo/InternalKeyboard/Open" ContextKit
value. You can do something like:
context-provide --session bogus.busname bool
Enter command "dump" and keep it running.
Then run meego-im-uiserver and the app:
CONTEXT_PROVIDERS=~ widgetsgallery -software
The keyboard state is monitored in libmeegotouch, MKeyboardStateTracker.
More information about the MeeGo-touch-dev