GTK is a multi-platform toolkit for creating graphical user interfaces.
Go to file
Owen Taylor 07f0382368 Mark child->window as destroyed so we don't destroy it again.
Sat Dec 12 17:46:55 1998  Owen Taylor  <otaylor@gtk.org>

	* gtk/gtklayout.c (gtk_layout_unrealize): Mark
	child->window as destroyed so we don't destroy
	it again.
1998-12-12 22:49:38 +00:00
debian Argh. Missed one dumb space in rules file. Fixed. 1998-11-18 06:25:35 +00:00
docs Released GTK+ 1.1.7 1998-12-11 06:12:24 +00:00
examples - re-write the GtkProgressBar section to the 1.1 API. - add an Appendix 1998-12-10 17:31:04 +00:00
gdk Corrections to computation of extents of text from a font set. (from 1998-12-12 22:21:48 +00:00
gtk Mark child->window as destroyed so we don't destroy it again. 1998-12-12 22:49:38 +00:00
tests avoid void pointer math 1998-12-11 05:52:42 +00:00
.cvsignore Merge from themes-2. See the ChangeLog for a somewhat detailed 1998-11-06 22:05:02 +00:00
acconfig.h use native Xlib XConvertCase if it's available 1998-06-28 05:44:14 +00:00
acinclude.m4 Explain check better. 1998-06-11 00:12:59 +00:00
AUTHORS Fixed some minor comment typos and added myself to AUTHORS in gtk+. 1998-08-06 04:09:40 +00:00
autogen.sh Replaced pushd and popd calls with equivalent shell code. 1998-11-25 17:13:14 +00:00
ChangeLog Mark child->window as destroyed so we don't destroy it again. 1998-12-12 22:49:38 +00:00
ChangeLog.pre-1-0 ChangeLog split up into ChangeLog.pre-1-0 and ChangeLog. 1998-04-17 01:07:36 +00:00
ChangeLog.pre-2-0 Mark child->window as destroyed so we don't destroy it again. 1998-12-12 22:49:38 +00:00
ChangeLog.pre-2-2 Mark child->window as destroyed so we don't destroy it again. 1998-12-12 22:49:38 +00:00
ChangeLog.pre-2-4 Mark child->window as destroyed so we don't destroy it again. 1998-12-12 22:49:38 +00:00
ChangeLog.pre-2-6 Mark child->window as destroyed so we don't destroy it again. 1998-12-12 22:49:38 +00:00
ChangeLog.pre-2-8 Mark child->window as destroyed so we don't destroy it again. 1998-12-12 22:49:38 +00:00
ChangeLog.pre-2-10 Mark child->window as destroyed so we don't destroy it again. 1998-12-12 22:49:38 +00:00
config.guess Update to libtool-1.2b, change library versioning scheme to drop 1998-09-17 15:40:22 +00:00
config.h.in Use gdk_window_get_origin() instead of gdk_window_get_position, because 1998-12-11 01:44:12 +00:00
config.sub Update to libtool-1.2b, change library versioning scheme to drop 1998-09-17 15:40:22 +00:00
configure.in Released GTK+ 1.1.7 1998-12-11 06:12:24 +00:00
COPYING Changed LGPL address for FSF in all .h and .c files 1998-04-13 02:02:47 +00:00
gtk-config.in Remove `#pragma }'. 1998-11-01 01:44:05 +00:00
gtk.m4 at Sep 12 10:44:06 1998 Owen Taylor <otaylor@redhat.com> 1998-09-12 14:41:04 +00:00
gtk+.spec Released GTK+ 1.1.7 1998-12-11 06:12:24 +00:00
HACKING HACKING we need libtool 1.2b now 1998-10-10 07:51:50 +00:00
INSTALL Released GTK+ 1.1.7 1998-12-11 06:12:24 +00:00
install-sh updated to latest automake version 1998-09-18 02:07:42 +00:00
ltconfig Update to libtool-1.2b, change library versioning scheme to drop 1998-09-17 15:40:22 +00:00
ltmain.sh Patch to libtool-1.2b to make --disable-static 1998-09-20 22:14:58 +00:00
makecopyright Changed LGPL address for FSF in all .h and .c files 1998-04-13 02:02:47 +00:00
Makefile.am Released GTK+ 1.1.6 1998-12-09 01:05:41 +00:00
missing updated to latest automake version 1998-09-18 02:07:42 +00:00
mkinstalldirs updated to latest automake version 1998-09-18 02:07:42 +00:00
NEWS Released GTK+ 1.1.7 1998-12-11 06:12:24 +00:00
NEWS.pre-1-0 ooops, fogot this on my last commit... 1998-05-07 07:45:04 +00:00
README Released GTK+ 1.1.7 1998-12-11 06:12:24 +00:00
README.cvs-commits Fixed argument list and return type for non-XIM fallback. 1998-12-09 18:13:52 +00:00
sanity_check configure.in: require GLib 1.1.5 1998-11-23 03:07:50 +00:00
stamp-h.in Initial revision 1997-11-24 22:37:52 +00:00
TODO reverted bogus and undocumented!!! changes from Jay Cox (98/11/23 1998-11-26 03:43:24 +00:00

General Information
===================

This is GTK+ version 1.1.7.   GTK+, which stands for the Gimp ToolKit, 
is a library for creating graphical user interfaces for the X Window 
System. It is designed to be small, efficient, and flexible. GTK+ is 
written in C with a very object-oriented approach.

The official ftp site is:
  ftp://ftp.gtk.org/pub/gtk

The official web site is:
  http://www.gtk.org/

A mailing list is located at:
  gtk-list@redhat.com

To subscribe: mail -s subscribe gtk-list-request@redhat.com < /dev/null
(Send mail to gtk-list-request@redhat.com with the subject "subscribe")

Installation
============

See the file 'INSTALL'

How to report bugs
==================

To report a bug, send mail either to gtk-list, as mentioned
above, or to gtk-bugs@gtk.org. If you send mail to gtk-list, you
must be subscribed yourself.

In the mail include:

* The version of GTK

* Information about your system. For instance:

   - What operating system and version
   - What version of X
   - For Linux, what version of the C library

  And anything else you think is relevant.

* How to reproduce the bug. 

  If you can reproduce it with the testgtk program that is built 
  in the gtk/ subdirectory, that will be most convenient.  Otherwise, 
  please include a short test program that exhibits the behavior. 
  As a last resort, you can also provide a pointer to a larger piece 
  of software that can be downloaded.

  (Bugs that can be reproduced within the  GIMP are almost as good 
  as bugs that can be reproduced in testgtk. If you are reporting a 
  bug found with the GIMP, please include the version number of the GIMP 
  you are using)

* If the bug was a crash, the exact text that was printed out
  when the crash occured.

* Further information such as stack traces may be useful, but
  is not necessary. If you do send a stack trace, and the error
  is an X error, it will be more useful if the stacktrace
  is produced running the test program with the --sync command
  line option.

Patches
=======

Patches can be uploaded to the incoming/ directory on
ftp.gtk.org.  Please follow the instructions there, and include
your name and email address in the README file.

If the patch fixes a bug, it is usually a good idea to include
all the information described in "How to Report Bugs".