|author||Havoc Pennington <firstname.lastname@example.org>||2001-10-13 04:15:25 +0000|
|committer||Havoc Pennington <email@example.com>||2001-10-13 04:15:25 +0000|
add bad hack to work with GTK 126.96.36.199 RPMs from gnomehide for now
2001-10-13 Havoc Pennington <firstname.lastname@example.org> * configure.in: add bad hack to work with GTK 188.8.131.52 RPMs from gnomehide for now * src/ui.c: another piece of bad hack in here
4 files changed, 29 insertions, 16 deletions
@@ -1,5 +1,12 @@
2001-10-13 Havoc Pennington <email@example.com>
+ * configure.in: add bad hack to work with GTK 184.108.40.206 RPMs from
+ gnomehide for now
+ * src/ui.c: another piece of bad hack in here
+2001-10-13 Havoc Pennington <firstname.lastname@example.org>
* configure.in: bump version
2001-10-13 Havoc Pennington <email@example.com>
@@ -9,24 +9,24 @@ your petty hangups about version numbers.
-You need GTK+ 1.3.x (to become 2.0), at least version 1.3.7. At the
+You need GTK+ 1.3.x (to become 2.0), at least version 1.3.9. At the
moment CVS HEAD works, but that can change. Metacity is a fairly
trivial 6000-line C program, so once you get GTK+ built it should be
no problem to build Metacity.
-There are SRPMs on the ftp site (there were also binaries for a bit,
-but I am taking them down because they only worked with Rawhide, so it
-was sort of pointless). Just "rpm --rebuild metacity-whatever.src.rpm"
-after installing the GTK packages from ftp.gtk.org.
+There are SRPMs and sometimes RPMs on the ftp site, but you'd be
+pretty lucky to get them to work for now, since they are often out of
+sync with GTK. You might try with the GTK from ftp.gtk.org, and also
+the GTK from http://people.redhat.com/hp/gnomehide/.
REPORTING BUGS AND SUBMITTING PATCHES
-Report new bugs to firstname.lastname@example.org for now. Will switch to Bugzilla
+Report new bugs on http://bugzilla.gnome.org.
Feel free to send patches too; Metacity is really small and simple, so
if you find a bug or want to add a feature it should be pretty easy.
+Send me mail, or put the patch in bugzilla.
See the HACKING file for some notes on hacking Metacity.
@@ -151,6 +151,8 @@ METACITY BUGS, NON-FEATURES, AND CAVEATS
clicking the minimize button is sort of a bad idea.
(If you had a WM-spec-compliant tasklist, it would work
+ (Update: you can use "test-wnck" from the libwnck CVS module to
+ unminimize, but it's not much of a UI ;-)
- Metacity uses the new window manager spec, but only random bits of
the old GNOME spec. It correctly advertises exactly which parts of
@@ -170,14 +172,7 @@ METACITY BUGS, NON-FEATURES, AND CAVEATS
instead of Alt as the main keybinding shortcut, if super/hyper
exist, and then keyboards with a windows key can use that for
WM functions and Alt for application shortcuts.
- We'd fall back to Alt if no other suitable modifier existed.
- - Cycling windows with Alt-Tab is flickery, AFAIK because
- Metacity passes the entire window stack to XRestackWindows()
- every time you restack. Instead it should probably only restack
- windows that have changed their stacking with respect to one
- another. (But sometimes I don't see the flicker, so
- I'm not sure.)
+ We'd fall back to Alt if no other suitable modifier existed.
- I haven't even read the ICCCM section about colormaps. So if you
have an 8-bit display you are basically screwed.
diff --git a/configure.in b/configure.in
index b3ae964..759d22f 100644
@@ -41,7 +41,7 @@ ALL_LINGUAS="sv"
## here we get the flags we'll actually use
-PKG_CHECK_MODULES(METACITY, gtk+-2.0 >= 1.3.7)
+PKG_CHECK_MODULES(METACITY, gtk+-2.0 >= 1.3.9)
@@ -75,6 +75,12 @@ fi
+## hack to work with old GTK versions for now
@@ -19,6 +19,7 @@
* 02111-1307, USA.
@@ -430,6 +431,10 @@ meta_ui_pop_delay_exposes (MetaUI *ui)
+#define gdk_pixbuf_new_from_inline gdk_pixbuf_new_from_stream
meta_ui_get_default_window_icon (MetaUI *ui)