GTK is a multi-platform toolkit for creating graphical user interfaces.
Go to file
Miguel de Icaza 21bb83612d Fix the problem introduced by whoever thought that randomly changing ints
1998-04-14  Miguel de Icaza  <miguel@nuclecu.unam.mx>

	* gdk/gdkwindow.c (gdk_window_xid_at): Fix the problem introduced
	by whoever thought that randomly changing ints to unsigned int
	without reviewing the code was a good idea.  It is, btw not
	mentioned in the ChangeLog as usual, but I know it was not Elliot
	the culprit this time.
1998-04-15 02:15:36 +00:00
debian Removed debian/files for real 1998-03-24 04:42:55 +00:00
docs Minor additions and fixes 1998-04-14 01:09:25 +00:00
examples Changed LGPL address for FSF in all .h and .c files 1998-04-13 02:02:47 +00:00
gdk Fix the problem introduced by whoever thought that randomly changing ints 1998-04-15 02:15:36 +00:00
glib Changed LGPL address for FSF in all .h and .c files 1998-04-13 02:02:47 +00:00
gtk Don't read the character past the end of the text. 1998-04-14 01:39:40 +00:00
tests removed duplicate call to gtk_widget_set_policy. 1998-04-13 19:09:00 +00:00
.cvsignore Removed gtk+-xconfig added gtk-config 1998-03-13 01:52:51 +00:00
acconfig.h define the version variables in config.h. 1998-03-08 02:04:26 +00:00
AUTHORS changes for 1.0.0 release. 1998-04-10 02:33:54 +00:00
autogen.sh I got sick of typing in the same commands over and over, so borrowed 1998-01-31 17:43:56 +00:00
ChangeLog Fix the problem introduced by whoever thought that randomly changing ints 1998-04-15 02:15:36 +00:00
ChangeLog.pre-2-0 Fix the problem introduced by whoever thought that randomly changing ints 1998-04-15 02:15:36 +00:00
ChangeLog.pre-2-2 Fix the problem introduced by whoever thought that randomly changing ints 1998-04-15 02:15:36 +00:00
ChangeLog.pre-2-4 Fix the problem introduced by whoever thought that randomly changing ints 1998-04-15 02:15:36 +00:00
ChangeLog.pre-2-6 Fix the problem introduced by whoever thought that randomly changing ints 1998-04-15 02:15:36 +00:00
ChangeLog.pre-2-8 Fix the problem introduced by whoever thought that randomly changing ints 1998-04-15 02:15:36 +00:00
ChangeLog.pre-2-10 Fix the problem introduced by whoever thought that randomly changing ints 1998-04-15 02:15:36 +00:00
config.guess Initial revision 1997-11-24 22:37:52 +00:00
config.h.in If the widget is _not_ a descendant of a Window widget, propagate key 1998-03-27 05:17:11 +00:00
config.sub Initial revision 1997-11-24 22:37:52 +00:00
configure.in changes for 1.0.0 release. 1998-04-10 02:33:54 +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 Make tab key move in reading order (left-to-right top to bottom) - which 1998-04-06 04:31:15 +00:00
gtk.m4 Added flags --prefix[=dir] and --exec-prefix[=DIR] which allow querying 1998-04-04 00:12:58 +00:00
gtk+.prj Initial revision 1997-11-24 22:37:52 +00:00
gtk+.spec Split out glib. 1998-04-13 17:36:45 +00:00
HACKING Updated package versions 1998-04-14 01:10:04 +00:00
INSTALL typo, gtk-1.0.0 should be gtk+-1.0.0 A little more intro on what gtk is... 1998-04-13 03:04:26 +00:00
install-sh Initial revision 1997-11-24 22:37:52 +00:00
ltconfig Moved glibconfig.h to $pkglibdir/include. Update to libtool-1.1. 1998-03-14 06:42:39 +00:00
ltmain.sh the Solaris ltconfig patch from draco 1998-03-19 22:35:51 +00:00
makecopyright Changed LGPL address for FSF in all .h and .c files 1998-04-13 02:02:47 +00:00
Makefile.am Changes for GTK+ 0.99.10 1998-04-08 04:07:01 +00:00
Makefile.in The auto_shrink policy of the floating window is now set to TRUE. This 1998-01-28 03:41:55 +00:00
missing Initial revision 1997-11-24 22:37:52 +00:00
mkinstalldirs Initial revision 1997-11-24 22:37:52 +00:00
NEWS changes for 1.0.0 release. 1998-04-10 02:33:54 +00:00
README update address info to gtk.org for ftp and web sites. 1998-04-14 01:05:16 +00:00
stamp-h.in Initial revision 1997-11-24 22:37:52 +00:00
TODO Minor additions and fixes 1998-04-14 01:09:25 +00:00

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

This is GTK+ version 1.0.0.   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".