Hi,
there is an API to detect if the window is in the foreground or not (thx to
Kimmo for pointing me to this) [1]. If this property is true, then the window
is visible on the screen. You can use this parameter directly from your root
window. And here [2] you find the method to get the value
On Fri, Jul 24, 2009 at 07:55, daniel wilmsdaniel.wi...@nokia.com wrote:
there is an API to detect if the window is in the foreground or not (thx to
Kimmo
for pointing me to this) [1]. If this property is true, then the window is
visible
on the screen. You can use this parameter directly
On Fri, 2009-07-24 at 10:54 +0200, ext Andrew Flegg wrote:
On Fri, Jul 24, 2009 at 07:55, daniel wilmsdaniel.wi...@nokia.com wrote:
there is an API to detect if the window is in the foreground or not (thx to
Kimmo
for pointing me to this) [1]. If this property is true, then the window is
2009/7/24 Kimmo Hämäläinen kimmo.hamalai...@nokia.com:
On Fri, 2009-07-24 at 10:54 +0200, ext Andrew Flegg wrote:
My basic code structure is:
* while timer fires:
- check is-topmost
- if false, cancel timer and return
Probably Python bindings are confused
On Fri, 2009-07-24 at 12:09 +0200, ext Andrew Flegg wrote:
2009/7/24 Kimmo Hämäläinen kimmo.hamalai...@nokia.com:
On Fri, 2009-07-24 at 10:54 +0200, ext Andrew Flegg wrote:
My basic code structure is:
* while timer fires:
- check is-topmost
- if false,
On Fri, Jul 24, 2009 at 4:54 AM, Andrew Fleggand...@bleb.org wrote:
On Fri, Jul 24, 2009 at 07:55, daniel wilmsdaniel.wi...@nokia.com wrote:
there is an API to detect if the window is in the foreground or not (thx to
Kimmo
for pointing me to this) [1]. If this property is true, then the
On Fri, Jul 24, 2009 at 11:57, Anderson
Lizardoanderson.liza...@openbossa.org wrote:
On Fri, Jul 24, 2009 at 4:54 AM, Andrew Fleggand...@bleb.org wrote:
Yup, indeed. (PyMaemo doesn't expose the method, but you can get the
property).
Hmm, here I can see this method just fine (Scratchbox X86
On Fri, Jul 24, 2009 at 7:12 AM, Andrew Fleggand...@bleb.org wrote:
Where's the latest PyMaemo documentation and API reference? Using the
C one is fine in most cases, but I'd like to see the Python specific
stuff wherever possible. The following seems to link to bora-level
documentation for
On Fri, Jul 24, 2009 at 13:17, Anderson
Lizardoanderson.liza...@openbossa.org wrote:
On Fri, Jul 24, 2009 at 7:12 AM, Andrew Fleggand...@bleb.org wrote:
It is at this same page, but on the top (Python Hildon Manual). I'll
fix the link to the python-hildon documentation to point the the newer
On Fri, Jul 24, 2009 at 8:57 AM, Andrew Fleggand...@bleb.org wrote:
On Fri, Jul 24, 2009 at 13:17, Anderson
Lizardoanderson.liza...@openbossa.org wrote:
Note that they may contain some errors, as they were partially
converted from C docs. Feel free to report any errors you find in our
On 2009-07-24 09:11, Anderson Lizardo anderson.liza...@openbossa.org wrote:
On Fri, Jul 24, 2009 at 8:57 AM, Andrew Fleggand...@bleb.org wrote:
On Fri, Jul 24, 2009 at 13:17, Anderson
Lizardoanderson.liza...@openbossa.org wrote:
Note that they may contain some errors, as they were partially
Hi,
ext Henrik Hedberg wrote:
There is a standard X event for that: XVisibilityEvent. The X server
(and a window manager) can keep window contents cached (backing store)
and decide not to send exposure events, but my interpretation is that if
it is not sending visibility events it is
On Sat, Jul 11, 2009 at 12:09, Andrew Fleggand...@bleb.org wrote:
On Sat, Jul 11, 2009 at 08:28, Faheem Perveztripp...@gmail.com wrote:
FocusOut event, serial 20, synthetic NO, window 0x161,
mode NotifyNormal, detail NotifyNonlinear
I had a thought about using focus-in/out and
For comparison:
A log of xev running on a desktop and minimizing the window:
FocusOut event, serial 34, synthetic NO, window 0x6c1,
mode NotifyNormal, detail NotifyNonlinear
UnmapNotify event, serial 34, synthetic NO, window 0x6c1,
event 0x6c1, window 0x6c1,
2009/7/10 Andrew Flegg and...@bleb.org:
Have you got any sample code which uses window-state-event I could use
as a basis for comparison?
See the function window_state_event at:
http://repo.or.cz/w/gpodder.git?a=blob;f=src/gpodder/gui.py;h=9b0d0bef53;hb=HEAD#l3323
In a more isolated and
On Sat, Jul 11, 2009 at 08:28, Faheem Perveztripp...@gmail.com wrote:
A log of xev running on a tablet running Diablo and minimizing the window:
PropertyNotify event, serial 20, synthetic NO, window 0x161,
atom 0xeb (WM_STATE), time 1756118079, state PropertyNewValue
I can't seem to
On Thu, Jul 9, 2009 at 09:47, Thomas Perlth.p...@gmail.com wrote:
For GTK+ (all languages), you probably want the window-state-event signal:
This works on my Ubuntu Jaunty system exactly as I'd expect: window
gets minimised and I can stop updates.
One thing I noted with the GTK+ flavour on
2009/7/8 Andrew Flegg and...@bleb.org:
2) Stop updating the screen when your app isn't in the
foreground.
- 8 ---
I'm willing to put together this wiki page but have two questions:
1) What is the best way of implementing (2) in C/Python/whatever?
For GTK+ (all
Andrew Flegg wrote 09.07.2009 00:29:
2) Stop updating the screen when your app isn't in the
foreground.
(1) is trivial to implement. (2) is trickier (there's
hildon_program_is_topmost() and hildon_window_is_topmost(), but
polling to discover when you're topmost again is
Hi,
the wiki page about this is a great idea and definitely needed. I will try to
collect some more ideas and perhaps we can discuss end of next week a bit in
IRC to collect the information?!?
Cheers Daniel
___
maemo-developers mailing list
On Thu, Jul 9, 2009 at 16:30, daniel wilmsdaniel.wi...@nokia.com wrote:
the wiki page about this is a great idea and definitely needed. I will try
to collect some more ideas and perhaps we can discuss end of next week a
bit in IRC to collect the information?!?
Perfect. I'll look at the
21 matches
Mail list logo
