[MeeGo-dev] QWidget::showEvent might be helpful for apps wanting to know if they should keep drawing.
sivan at omniqueue.com
Fri Nov 12 14:44:54 PST 2010
Let's do it then. We already have the user story:
Joe wants to know when his application's window is not to be
considered "visible" == "not worth drawing or updating in UI tems"
(this can be obscured, less then 20% visible when pushed sideways,
screen is locked, display off).
Jow wants to know when his app is visible again (not obscured, display
on, brought back from the sides)
It feels to me it might be non trivial to merge all the raw states to
two events in a qt api, but as we discussed the benefit will be both
in power and performance consumption and standardized API, if we could
have it also implemented on the other targets (Symbian et al).
On Sat, Nov 13, 2010 at 12:36 AM, Andy Ross <andy at plausible.org> wrote:
> On 11/12/2010 12:01 PM, Thiago Macieira wrote:
>> On Friday, 12 de November de 2010 20:09:04 Arjan van de Ven wrote:
>> > can we get some urgency on solving this? adding events for "you're
>> > visible" and "you're not visible" ?
>> > It's a huge deal for power / thermal savings.....
>> What event does the WM send? What X event does the app receive?
> To (hopefully, at least to the extent of my understanding) clarify:
> there's nothing in X11 that would give you that unambiguously. An
> Expose event tells you when a region transitions from obscured to
> visible, but not the reverse. The DAMAGE extension tells you
> something like the reverse, but you'd then have to do tricks like
> walking the window hierarchy to figure out what happened. Maybe these
> could be hacked to work together, but I don't know the details.
> The window manager *does* have this information (albeit only for
> top-level windows), but there's no standard in place for how it should
> tell apps. So presumably someone has to do some architecture work
> first? I'm no X11 expert, but it strikes me as a solvable problem to
> define and emit a WM-specific client message.
> MeeGo-dev mailing list
> MeeGo-dev at meego.com
More information about the MeeGo-dev