From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: yocto@yoctoproject.org
Subject: Re: Matchbox keyboard
Date: Tue, 05 Feb 2013 21:12:05 +0000 [thread overview]
Message-ID: <511175A5.30309@r-finger.com> (raw)
In-Reply-To: <51115B5D.5000509@mlbassoc.com>
On 05/02/13 19:19, Gary Thomas wrote:
> On 2013-02-05 12:00, Tomas Frydrych wrote:
>> On 05/02/13 18:47, Gary Thomas wrote:
>>> Sorry if this isn't the best place to ask...
>>>
>>> I have a GUI application running on Poky/Yocto with Sato using
>>> only a touch screen. My application window takes up the whole
>>> display which is *very* small (320x240). If I try and accept
>>> text input, I can see the matchbox keyboard try to pop up, but
>>> it immediately ends up behind my application window and thus
>>> is of little use :-(
>>
>> This should not be too small, I am pretty sure I have used it on a
>> device of that size, but it assumes the GUI application is well behaved
>> and obeys the window manager -- you have to make it respect the size the
>> WM allocates.
>
> Does the window manager attempt to resize my window when the keyboard
> pops up? I have a simple dialog and I don't see it being resized (if
> that's even possible)
In the matchbox case it works through the window stack and works out the
size that is taken up by DOCKS and TOOLBARS (the kbd is a toolbar,
iirc); whatever is left is then given to the other windows (applications
and dialogs). Simplest way to verify if the WM is trying to resize the
dialog is to listen for the ConfigureNotify event and see what sizes are
coming through there (how you do that would depend on the toolkit).
Tomas
--
http://sleepfive.com
prev parent reply other threads:[~2013-02-05 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 18:47 Matchbox keyboard Gary Thomas
2013-02-05 19:00 ` Tomas Frydrych
2013-02-05 19:19 ` Gary Thomas
2013-02-05 21:12 ` Tomas Frydrych [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=511175A5.30309@r-finger.com \
--to=tf+lists.yocto@r-finger.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.