GTK is a multi-platform toolkit for creating graphical user interfaces.
Go to file
Owen Taylor 16561707f8 Always set the max width or height to at least 1, since 0 triggers bugs in
Sun Feb 21 17:14:44 1999  Owen Taylor  <otaylor@redhat.com>

	* gdk/gdkwindow.c (gdk_window_set_geometry_hints): Always
	 set the max width or height to at least 1, since 0
	 triggers bugs in some window managers. (The window
	"pops out" of the frame in fvwm)
1999-02-21 22:12:00 +00:00
debian Argh. Missed one dumb space in rules file. Fixed. 1998-11-18 06:25:35 +00:00
docs version = 1.1.16 1999-02-16 21:25:25 +00:00
examples add SpinButton example 1999-02-08 13:10:10 +00:00
gdk Always set the max width or height to at least 1, since 0 triggers bugs in 1999-02-21 22:12:00 +00:00
gdk-pixbuf Stuff I did last night while watching TV 1999-01-05 21:27:07 +00:00
gtk Changed warnings from g_message() to g_warning(). 1999-02-21 21:24:02 +00:00
po Shooby Ban <bansz@szif.hu> 1999-02-17 07:19:53 +00:00
tests Use a ScrolledWindow test how Text widgets work within ScrolledWindow. 1999-02-16 04:52:21 +00:00
.cvsignore cvs be quiet 1999-01-13 19:17:08 +00:00
acconfig.h If we can't find helvetica, fall back to "fixed". If we can't find 1999-02-10 00:21:09 +00:00
acinclude.m4 Xsed isn't valid here, don't use it 1999-01-28 04:58:01 +00:00
AUTHORS s,Fedrerico Mena,Federico Mena, 1998-12-24 12:33:19 +00:00
autogen.sh Remove autogenned files 1999-02-01 22:50:07 +00:00
ChangeLog Always set the max width or height to at least 1, since 0 triggers bugs in 1999-02-21 22:12:00 +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 Always set the max width or height to at least 1, since 0 triggers bugs in 1999-02-21 22:12:00 +00:00
ChangeLog.pre-2-2 Always set the max width or height to at least 1, since 0 triggers bugs in 1999-02-21 22:12:00 +00:00
ChangeLog.pre-2-4 Always set the max width or height to at least 1, since 0 triggers bugs in 1999-02-21 22:12:00 +00:00
ChangeLog.pre-2-6 Always set the max width or height to at least 1, since 0 triggers bugs in 1999-02-21 22:12:00 +00:00
ChangeLog.pre-2-8 Always set the max width or height to at least 1, since 0 triggers bugs in 1999-02-21 22:12:00 +00:00
ChangeLog.pre-2-10 Always set the max width or height to at least 1, since 0 triggers bugs in 1999-02-21 22:12:00 +00:00
config.guess acinclude.m4 ltconfig upgrade to libtool 1.2d (with fixes for irix6 and 1999-01-13 06:53:26 +00:00
config.sub acinclude.m4 ltconfig upgrade to libtool 1.2d (with fixes for irix6 and 1999-01-13 06:53:26 +00:00
configure.in I've made the spec file autogenerated and I updated the file list 1999-02-21 21:00:23 +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 Pass gthread on to gtk-config. 1999-02-01 23:17:39 +00:00
gtk.m4 Fix glib_config_args gtk_config_args confusion. (pointed out by Roland 1999-02-18 16:43:42 +00:00
gtk+.spec.in I've made the spec file autogenerated and I updated the file list 1999-02-21 21:00:23 +00:00
HACKING - GNU autoconf 2.13 - GNU automake 1.4 (Beta releases are at 1999-01-17 16:54:58 +00:00
INSTALL version = 1.1.16 1999-02-16 21:25:25 +00:00
ltconfig Xsed isn't valid here, don't use it 1999-01-28 04:58:01 +00:00
ltmain.sh Xsed isn't valid here, don't use it 1999-01-28 04:58:01 +00:00
makecopyright Changed LGPL address for FSF in all .h and .c files 1998-04-13 02:02:47 +00:00
Makefile.am I've made the spec file autogenerated and I updated the file list 1999-02-21 21:00:23 +00:00
NEWS Updated for 1.1.16. 1999-02-16 03:50:09 +00:00
NEWS.pre-1-0 ooops, fogot this on my last commit... 1998-05-07 07:45:04 +00:00
README version = 1.1.16 1999-02-16 21:25:25 +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
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.16.   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".