The only way I know to do that is by calling window.set_accept_focus(False)
before window.show(). The serious flaw with that method is that the
resulting window, while being prevented from stealing the focus, also can
not receive focus at any later time, even by intentional user action.
What
On Thu, 22 May 2008 17:26:15 -0700 Tom Machinski wrote:
Hi,
I wrote a simple GTK+ application that displays a popup window.
The problem is that whenever the window is displayed, it immediately
gets (steals) the focus. I would like to prevent that from
happening: i.e., the window should
On Thu, May 22, 2008 at 11:22 PM, Tiberius DULUMAN
[EMAIL PROTECTED] wrote:
The only way I know to do that is by calling
window.set_accept_focus(False)
before window.show(). The serious flaw with that method is that the
resulting window, while being prevented from stealing the focus, also
On Thu, May 22, 2008 at 11:52 PM, Brian J. Tarricone [EMAIL PROTECTED]
wrote:
gtk_window_set_focus_on_map() (or presumably
window.set_focus_on_map(False) in... whatever langauges you're using).
Thanks Brian, aniket. Unfortunately, this solution does not work.
`dpkg -l libgtk2.0-0` shows the
Tom Machinski wrote:
On Thu, May 22, 2008 at 11:52 PM, Brian J. Tarricone [EMAIL PROTECTED]
wrote:
gtk_window_set_focus_on_map() (or presumably
window.set_focus_on_map(False) in... whatever langauges you're using).
Thanks Brian, aniket. Unfortunately, this solution does not work.
On Fri, May 23, 2008 at 9:52 AM, Brian J. Tarricone [EMAIL PROTECTED]
wrote:
Well, it works here, using straight C. I don't really know Python, so I
can't really say why it wouldn't work there.
Thanks a lot Brian. Could you perchance paste the code you used? If this is
a bug in PyGTK, it
Am Freitag, den 02.05.2008, 12:59 -0400 schrieb Randy Poe:
The fact that they happen when they do suggests they are associated
with clean-up code. Did you write some of your own *_finalize or
*_destroy routine to clean up memory you allocated? Or did you
otherwise write some code which is
Tom Machinski wrote:
On Fri, May 23, 2008 at 9:52 AM, Brian J. Tarricone [EMAIL PROTECTED]
wrote:
Well, it works here, using straight C. I don't really know Python, so I
can't really say why it wouldn't work there.
Thanks a lot Brian. Could you perchance paste the code you used? If
On Fri, May 23, 2008 at 2:26 PM, Brian J. Tarricone [EMAIL PROTECTED]
wrote:
Hmm, when I write basically the same thing as your Python implementation
in C, I get the same result as you -- the window grabs focus when it's
shown.
OK, so I've compiled and ran both your code below, and a
Tom Machinski [EMAIL PROTECTED] writes:
On Fri, May 23, 2008 at 2:26 PM, Brian J. Tarricone [EMAIL PROTECTED]
wrote:
Hmm, when I write basically the same thing as your Python implementation
in C, I get the same result as you -- the window grabs focus when it's
shown.
OK, so I've
Andreas Nilsson wrote:
The tutorials are hosted on Library, and I'm unsure what's the policy is
there.
Does anyone on this list know?
If I remember correctly, the tutorial is kept in the GTK+ source and
used to be copied to the gtk.org infrastructure and uploaded that way.
Now it is hosted on
On Fri, May 23, 2008 at 10:38:15AM +0100, Martyn Russell wrote:
Now it is hosted on library.gnome.org I would guess it is generated
automatically from the source + docbook? I don't actually know. Anyone
care to fill us in, we have someone ready and willing to update it :)
Library uses
Olav Vitters wrote:
Library uses tarballs. When you do a install-module, library.gnome.org
updates after a while (5 min cron delay). Might not always take the
latest version though (uses the r-t modulesets IIRC, something like
micro being ok, but won't take newer major.. ask frepd if you want
13 matches
Mail list logo
