Re: Find out if window is active
Doesnt work here either. The window becomes active when i focus it for
the first time, after wards the callback is never called again.
On 15/04/13 02:06, Matthias Clasen wrote:
g_signal_connect (window, notify::is-active,
G_CALLBACK (print_active), NULL);
with
static void
print_active (GtkWindow *window)
{
g_print (active: %d\n, gtk_window_is_active (window));
}
works as expected here, and prints active: 1 and active: 0 as the
window becomes active or inactive.
___
gtk-devel-list mailing list
gtk-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-devel-list
Re: Find out if window is active
Sounds like you possibly found a bug, then. Which platform is this on ? ___ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
Re: Bug 696632 - dead circumflex is not printed as ^
Hi Matthias On Wed, 2013-03-27 at 14:53 +, Ritesh Khadgaray wrote: Hi Is it possible to review the attach patch[1] ? Thank you [1] https://bugzilla.gnome.org/show_bug.cgi?id=696632 Thank you for the review. I have posted my thoughts. -- --ritz (medicine) % Death has been proven to be 99% fatal in laboratory rats. ___ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
Fwd: Re: Find out if window is active
I am using metacity and gnome-panel. I can try switching to mutter or compiz and see if that will fix the problem. Does the behaviour of this function depend of the window manager that im using? On 15/04/13 14:30, Matthias Clasen wrote: Sounds like you possibly found a bug, then. Which platform is this on ? ___ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
hackfest preparations
Over the last few days, I've done some editing of https://live.gnome.org/Hackfests/GTK2013 - there's some more detail about the topics now (please add more, if you have thoughts) I have now confirmed that we can use the OLPC office; lets meet there Friday morning around 10am and get started.The address is on the wiki Matthias ___ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
Re: GTK+3 win32/64 build environment
On 04/13/2013 07:37 PM, tarn...@tarnyko.net wrote: As a majority of you told me it was so easy and effective to cross-compile from Linux, rather than doing it navitely on Windows, I finally felt like trying it. Well, after some hacking... you were right ^^. I extracted my GTK+3 buildenv on my favorite Linux distro, installed some packages, adapted some scripts, hacked around 2-3 specific problems, and it ran just fine. Now I've got a complete GTK+3 Win32 bundle, generated from Linux. So now we have two fast-identical buildenvs, one for Windows and one for Linux. Just a drawback : like I previously said, cross-compiling GTK+3 from Linux requires to build the stack twice. It's no big deal, just that the Linux buildenv has more specific scripts -I'm currently rewriting them. I will upload all scripts to Git as soon as I get my account approved. Thanks a lot for your advices. Thanks for doing all this hard work. We'll all benefit from in. Question for you and for other windows GTK developers. Is it desirable to continue to compile against msvcrt.dll instead of a more recent, VS-compatible version? Is the issue simply one of licensing for the dll itself (IE distributing it to Linux environments to compile against is not permitted)? Of course this problem of incompatible msvcrt dlls goes well beyond GTK. All windows projects have to deal with this issue. A distribution of Python might be compiled with VS 2008, and the developer writing C api python modules might be using VS 2009. Maybe there's not a good solution in general. ___ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
