It certianly is great to be reading this, now GTK has a good file selector and it’s a lot faster, I shall recompile Gnome tonight and get a good feel for it.
And besides, recompiling gnome won’t give you the new file selector either. I think it’s up to the application to take advantage of that. You’d need GNOME 2.5.x to get that.
Please do not upgrade an existing GTK install if you use GNOME 2.4 or lower. GObject made a semantic change to one of the APIs which makes a non-fatal bug a fatal one in a component of gnome related to session management, which will cause a “hang” on logout (the X server will stop accepting input, effectively). Therefore only upgrade GTK if you are upgrading GNOME at the same time.
“Please do not upgrade an existing GTK install if you use GNOME 2.4”
What about using GTK 2.4 under KDE for the various GTK apps? Will I run into the problems with backwards compatibility or is that just a problem with the Gnome DE?
What I am really looking at is Firefox. There has long been a problem with the flash plugin when Firefox uses GTK2 and I would like to find out if this bug is now fixed.
Yes and no. Since 2.4 is binary-compatible with 2.2, GNOME will run just fine with 2.4. However, most GNOME apps will continue to use the old file dialog until their source is updated to use the new API.
The new dialog is different enough that it has a seperate API than the old one. The old API apparently was insufficient to support the functionality of the new dialog.
I find that X “locks” when logging outa t times, I have found that if I go through the different virtual desktops (CTRL + ALT + arrow keys), it will then log out.
NO idea why it is like this, but 19 times out of 20 it works.
Gtk# is currently targetting GTK+ 2.2 (or 2.0, I forget), as that version is present on most developers and users machines. This will likely remain the case until Mono 1.0 and Gtk# 1.0, at which point Gtk# will start tracking the latest GTK+ release.
It certianly is great to be reading this, now GTK has a good file selector and it’s a lot faster, I shall recompile Gnome tonight and get a good feel for it.
Why recompile GNOME? GTK 2.4 is binary and API compatible with 2.2 and other releases.
You should recompile only if you’ll get a newer GNOME such as 2.5.91 or something…
And besides, recompiling gnome won’t give you the new file selector either. I think it’s up to the application to take advantage of that. You’d need GNOME 2.5.x to get that.
Please do not upgrade an existing GTK install if you use GNOME 2.4 or lower. GObject made a semantic change to one of the APIs which makes a non-fatal bug a fatal one in a component of gnome related to session management, which will cause a “hang” on logout (the X server will stop accepting input, effectively). Therefore only upgrade GTK if you are upgrading GNOME at the same time.
<quote>You’d need GNOME 2.5.x to get that.</quote>
or Screem-0.9.5
http://www.screem.org/development.php
“Please do not upgrade an existing GTK install if you use GNOME 2.4”
What about using GTK 2.4 under KDE for the various GTK apps? Will I run into the problems with backwards compatibility or is that just a problem with the Gnome DE?
What I am really looking at is Firefox. There has long been a problem with the flash plugin when Firefox uses GTK2 and I would like to find out if this bug is now fixed.
Simon
Hi Mike,
That sounds remarkably like an issue i get intermitantly on my Fedora Core 1 machine (all updates from Fedora/Dag/FreshRPMs applied).
Is there any way this could be causing my machine to lockup?
X hangs when i log out on occasion, and on booting at the GDM screen on occasion. In both instances, i get a black unresponsive screen.
I know this isn’t tech support, but it sounded so similar to my problem, i had to ask.
Didn’t see any mention in the Changelog. How about those listboxes with the bad tearing.
did someone try if the new gtk is faster at drawing ? The older one was a little bit sluggish. I only head that the new tree widget would be fast …
Question:
Is GNOME 2.6 based on GTK 2.4.0?
Cause I see GNOME betas were released before GTK 2.4
Another question:
Does GTK# use GTK 2.4.0?
Yes and no. Since 2.4 is binary-compatible with 2.2, GNOME will run just fine with 2.4. However, most GNOME apps will continue to use the old file dialog until their source is updated to use the new API.
This is a point release, why would it have a new API.
Also, why would the source need to be change dto use new dialogs. If the classes have the same names won’t the application just automatically use it?
The new dialog is different enough that it has a seperate API than the old one. The old API apparently was insufficient to support the functionality of the new dialog.
I find that X “locks” when logging outa t times, I have found that if I go through the different virtual desktops (CTRL + ALT + arrow keys), it will then log out.
NO idea why it is like this, but 19 times out of 20 it works.
Doug
How can I change the button order of the dialog-boxes?
Ok, I run RH 8.0 with Ximian Desktop 2. Upgraded to
GTK+2.4 now, no problems so far.
Gtk# is currently targetting GTK+ 2.2 (or 2.0, I forget), as that version is present on most developers and users machines. This will likely remain the case until Mono 1.0 and Gtk# 1.0, at which point Gtk# will start tracking the latest GTK+ release.