Go to file
Owen Taylor 7f0156c2ea Optimization - when we've already found a widget, skip all checks for
Tue Dec 22 14:50:25 1998  Owen Taylor  <otaylor@redhat.com>

	* gtk/gtkdnd.c (gtk_drag_find_widget): Optimization -
	when we've already found a widget, skip all checks
	for subsequent children.

	* gtk/gtkdnd.c (gtk_drag_find_widget): Checked for
	!MAPPED, not !VISIBLE, since a widget (like a notebook
	page), can be VISIBLE, but !REALIZED or !MAPPED.

	* gtk/gtkdnd.c (gtk_drag_find_widget): Use forall(),
	not foreach().
1998-12-22 20:06:44 +00:00
debian
docs Released GTK+ 1.1.9 1998-12-17 06:49:15 +00:00
examples
gdk export the priority at which events are processed. 1998-12-20 05:47:28 +00:00
gtk Optimization - when we've already found a widget, skip all checks for 1998-12-22 20:06:44 +00:00
po Added translation by Krzysztof Krzy¿aniak <eloy@venco.com.pl> 1998-12-22 19:25:40 +00:00
tests Free previous label->label_wc. 1998-12-17 15:51:15 +00:00
.cvsignore
acconfig.h
acinclude.m4 Make the gettext check for for libc5 systems. 1998-12-15 23:11:05 +00:00
AUTHORS
autogen.sh rm -rf intl breaks --disable-nls, put it back 1998-12-17 05:21:45 +00:00
ChangeLog Optimization - when we've already found a widget, skip all checks for 1998-12-22 20:06:44 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-2-0 Optimization - when we've already found a widget, skip all checks for 1998-12-22 20:06:44 +00:00
ChangeLog.pre-2-2 Optimization - when we've already found a widget, skip all checks for 1998-12-22 20:06:44 +00:00
ChangeLog.pre-2-4 Optimization - when we've already found a widget, skip all checks for 1998-12-22 20:06:44 +00:00
ChangeLog.pre-2-6 Optimization - when we've already found a widget, skip all checks for 1998-12-22 20:06:44 +00:00
ChangeLog.pre-2-8 Optimization - when we've already found a widget, skip all checks for 1998-12-22 20:06:44 +00:00
ChangeLog.pre-2-10 Optimization - when we've already found a widget, skip all checks for 1998-12-22 20:06:44 +00:00
config.guess
config.h.in
config.sub
configure.in Added translation by Krzysztof Krzy¿aniak <eloy@venco.com.pl> 1998-12-22 19:25:40 +00:00
COPYING
gtk-config.in Add @INTLLIBS@. gtk-scier-981116-0.patch Sean Cier 1998-12-18 01:32:33 +00:00
gtk.m4
gtk+.spec Released GTK+ 1.1.9 1998-12-17 06:49:15 +00:00
HACKING
INSTALL Released GTK+ 1.1.9 1998-12-17 06:49:15 +00:00
install-sh
ltconfig
ltmain.sh
makecopyright
Makefile.am Provide a hacked version of the gettext macros that never use the included 1998-12-15 21:08:52 +00:00
missing
mkinstalldirs
NEWS Released GTK+ 1.1.9 1998-12-17 06:49:15 +00:00
NEWS.pre-1-0
README Released GTK+ 1.1.9 1998-12-17 06:49:15 +00:00
README.cvs-commits
sanity_check
stamp-h.in
TODO

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

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