[MeeGo-touch-dev] Any way t o force virtual keyboard to be used?
danny
tornadory at 163.com
Tue Aug 3 22:46:23 PDT 2010
Hi,
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.
--
Best Regards,
>I'm in a situation where I need to be testing the use of the VKBD but
>on a device that has a HW KBD and no "open"/"close" state.
>
>During daily ongoing development of meego-handset-dialer, I tend to
>code->build->install->test->code->... in rapid progression on my
>laptop/netbook (running MeeGo of course) for efficiency. As such, I'd
>love to just provide a command line option (like "-target Aava") or set
>a GConf key, or notify a ContextKit provider, or ... so that I can
>force the keyboard behavior.
>
>I've looked in the mtf sources, seen the recent changes to specify VKBD
>orientation locking in the devices.conf, but do not find any (obvious)
>means of hard setting the use of the VKBD.
>
>Other places I've started to look but have, as of yet, failed to find
>clues are in ContextKit providers (meego and maemo),
>inputmethodkeyboard and inputmethodframework, libmeegotouch and a few
>other random projects.
>
>In inputmethodkeyboard I can see where MKeyboardHost::setState() is
>defined, but it's entirely lost to me how, when or if this is ever
>called and if so, by what?
>
>In short, is there *ANY* way (for development purposes only) to force
>the use and loading of the virtual keyboard even when there is a
>physical keyboard present? A GConf key, a properly crafted DBus
>message, an XOrg or udev config, ... ?
>
>Shane...
>_______________________________________________
>MeeGo-touch-dev mailing list
>MeeGo-touch-dev at meego.com
>http://lists.meego.com/listinfo/meego-touch-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.meego.com/pipermail/meego-touch-dev/attachments/20100804/b37b436d/attachment.html>
More information about the MeeGo-touch-dev
mailing list