Go to file
Owen Taylor 58e63f08ae Revise algorithm for scrolling backwards. This one might actually work
Sun Feb 21 11:39:06 1999  Owen Taylor  <otaylor@redhat.com>

	* gtk/gtktext.c (find_line_containing_point): Revise
	algorithm for scrolling backwards. This one might actually
	work with one-line-high	Text widgets.

	* gtk/gtkmain.c: Removed a misplaced comment, a few
	formatting cleanups.
1999-02-21 18:02:14 +00:00
debian
docs
examples
gdk
gdk-pixbuf
gtk Revise algorithm for scrolling backwards. This one might actually work 1999-02-21 18:02:14 +00:00
po Shooby Ban <bansz@szif.hu> 1999-02-17 07:19:53 +00:00
tests
.cvsignore
acconfig.h
acinclude.m4
AUTHORS
autogen.sh
ChangeLog Revise algorithm for scrolling backwards. This one might actually work 1999-02-21 18:02:14 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-2-0 Revise algorithm for scrolling backwards. This one might actually work 1999-02-21 18:02:14 +00:00
ChangeLog.pre-2-2 Revise algorithm for scrolling backwards. This one might actually work 1999-02-21 18:02:14 +00:00
ChangeLog.pre-2-4 Revise algorithm for scrolling backwards. This one might actually work 1999-02-21 18:02:14 +00:00
ChangeLog.pre-2-6 Revise algorithm for scrolling backwards. This one might actually work 1999-02-21 18:02:14 +00:00
ChangeLog.pre-2-8 Revise algorithm for scrolling backwards. This one might actually work 1999-02-21 18:02:14 +00:00
ChangeLog.pre-2-10 Revise algorithm for scrolling backwards. This one might actually work 1999-02-21 18:02:14 +00:00
config.guess
config.sub
configure.in Shooby Ban <bansz@szif.hu> 1999-02-16 22:25:54 +00:00
COPYING
gtk-config.in
gtk.m4 Fix glib_config_args gtk_config_args confusion. (pointed out by Roland 1999-02-18 16:43:42 +00:00
gtk+.spec
HACKING
INSTALL
ltconfig
ltmain.sh
makecopyright
Makefile.am
NEWS
NEWS.pre-1-0
README
README.cvs-commits
sanity_check
TODO

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".