[MeeGo-touch-dev] Help: How to make the VKB shown in the meego-handset simulation env. ?
tornadory at 163.com
Wed Aug 18 03:14:15 PDT 2010
Thanks a lot, and I will try the mcompositor you mentioned, but I don't know how to check out the
commit id ea0fbb684a42ef2a2cd027dddbe81d86c0167be5 using git, could you tell me?
And I found another phenomenon:
If I use the two chroot env. at the same time, one is v0629 and the other is v0810, if i run meego-im-uiserver in the v0629, and run sms in the v0810 env. then I can also see the VKB, but if I exit the env. v0629 then nothing is shown.
At 2010-08-18 16:58:51，"Jani Mikkonen" <jani.3.mikkonen at nokia.com> wrote:
>> I want to know how could make the VKB shown in the simulation env.
>Are you talking about meegotouch ux ? If yes, default window manager has
>bugs relating to software rendering in this area. It was working last
>week just fine (allthou a bit slowly but it got broken again).
>Developers are aware of this issue but i cant say - as i don't know -
>when those will be fixed.
>If you want to try, checkout a mcompositor from gitorious and then
>checkout commit id ea0fbb684a42ef2a2cd027dddbe81d86c0167be5 . Atleast
>for me, that version works with virtual keyboard of all related daemons
>are started with -software paremeter (mcompositor, mdecorator,
>meego-im-uiserver - also meego-im-uiserver should have -bypass-wm-hint
>> I found that no way to make the VKB shown, how do you test it? all
>> should in one handset device?
>Currently, testing happens only on hardware but since im a sort of s.o.b
>and dont believe in often heard mantra of "we dont make software for
>scratchbox", i keep on filing bugs to make things work so that people
>can actually write and test their software without the device too.
>PS. In a meanwhile, file a bug and hope for a best.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MeeGo-touch-dev