Go to file
Manish Singh 3c07b7ebbd check if column[i].button is valid before calling gtk_widget_intersect on
* gtk/gtkclist.c: check if column[i].button is valid before calling
gtk_widget_intersect on it in gtk_clist_draw

* gtk/gtkdnd.c: removed unused variable empty_bits

* gtk/gtkrc.c: we should use gslist_* functions with GSLists...

* gtk/gtktypeutils.[ch]: makes more send for gtk_type_is_a to return
a boolean (thanks to Elrond for noticing this)

-Yosh
1998-11-08 05:58:41 +00:00
debian
docs Merge from themes-2. See the ChangeLog for a somewhat detailed 1998-11-06 22:05:02 +00:00
examples forward declaration for gtk_window_paint declare xid_ht static get the 1998-11-07 16:12:37 +00:00
gdk forward declaration for gtk_window_paint declare xid_ht static get the 1998-11-07 16:12:37 +00:00
gtk check if column[i].button is valid before calling gtk_widget_intersect on 1998-11-08 05:58:41 +00:00
tests check if column[i].button is valid before calling gtk_widget_intersect on 1998-11-08 05:58:41 +00:00
.cvsignore Merge from themes-2. See the ChangeLog for a somewhat detailed 1998-11-06 22:05:02 +00:00
acconfig.h
acinclude.m4
AUTHORS
autogen.sh fixed xlc stuff 1998-10-26 03:12:19 +00:00
ChangeLog check if column[i].button is valid before calling gtk_widget_intersect on 1998-11-08 05:58:41 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-2-0 check if column[i].button is valid before calling gtk_widget_intersect on 1998-11-08 05:58:41 +00:00
ChangeLog.pre-2-2 check if column[i].button is valid before calling gtk_widget_intersect on 1998-11-08 05:58:41 +00:00
ChangeLog.pre-2-4 check if column[i].button is valid before calling gtk_widget_intersect on 1998-11-08 05:58:41 +00:00
ChangeLog.pre-2-6 check if column[i].button is valid before calling gtk_widget_intersect on 1998-11-08 05:58:41 +00:00
ChangeLog.pre-2-8 check if column[i].button is valid before calling gtk_widget_intersect on 1998-11-08 05:58:41 +00:00
ChangeLog.pre-2-10 check if column[i].button is valid before calling gtk_widget_intersect on 1998-11-08 05:58:41 +00:00
config.guess
config.h.in Merge from themes-2. See the ChangeLog for a somewhat detailed 1998-11-06 22:05:02 +00:00
config.sub
configure.in Merge from themes-2. See the ChangeLog for a somewhat detailed 1998-11-06 22:05:02 +00:00
COPYING
gtk-config.in Remove `#pragma }'. 1998-11-01 01:44:05 +00:00
gtk.m4
gtk+.spec Released GTK+ 1.1.3 1998-10-31 09:53:29 +00:00
HACKING
INSTALL Released GTK+ 1.1.3 1998-10-31 09:53:29 +00:00
install-sh
ltconfig
ltmain.sh
makecopyright
Makefile.am Released GTK+ 1.1.3 1998-10-31 09:53:29 +00:00
missing
mkinstalldirs
NEWS Released GTK+ 1.1.3 1998-10-31 09:53:29 +00:00
NEWS.pre-1-0
README Released GTK+ 1.1.3 1998-10-31 09:53:29 +00:00
README.cvs-commits
sanity_check Released GTK+ 1.1.3 1998-10-31 09:53:29 +00:00
stamp-h.in
TODO Merge from themes-2. See the ChangeLog for a somewhat detailed 1998-11-06 22:05:02 +00:00

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

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