Go to file
jacob berkman eb037279db don't cast a PIXTEXT cell to a PIXMAP cell (fixes crash when using PIXTEXT
2001-10-22  jacob berkman  <jacob@ximian.com>

	* gtk/gtkclist.c (cell_size_request): don't cast a PIXTEXT cell to
	a PIXMAP cell (fixes crash when using PIXTEXT cells)
2001-10-22 17:01:11 +00:00
contrib
debian
demos at Oct 20 19:38:16 2001 Owen Taylor <otaylor@redhat.com> 2001-10-20 23:39:32 +00:00
docs Remove note about deprecation. (We've standard on G_CONST_RETURN rather 2001-10-22 14:28:37 +00:00
examples
gdk Deprecate gtk_entry_set_editable. (#58768, Vitaly Tishkov) 2001-10-22 14:31:06 +00:00
gdk-pixbuf
gtk don't cast a PIXTEXT cell to a PIXMAP cell (fixes crash when using PIXTEXT 2001-10-22 17:01:11 +00:00
m4macros
modules
po Update based on norwegian 2001-10-20 21:47:54 +00:00
tests Fix problem with g_return_if_fail return value. 2001-10-22 04:34:42 +00:00
.cvsignore correct docs for use_align 2001-10-19 20:46:43 +00:00
acconfig.h
acinclude.m4
AUTHORS
autogen.sh
ChangeLog don't cast a PIXTEXT cell to a PIXMAP cell (fixes crash when using PIXTEXT 2001-10-22 17:01:11 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-1-2
ChangeLog.pre-2-0 don't cast a PIXTEXT cell to a PIXMAP cell (fixes crash when using PIXTEXT 2001-10-22 17:01:11 +00:00
ChangeLog.pre-2-2 don't cast a PIXTEXT cell to a PIXMAP cell (fixes crash when using PIXTEXT 2001-10-22 17:01:11 +00:00
ChangeLog.pre-2-4 don't cast a PIXTEXT cell to a PIXMAP cell (fixes crash when using PIXTEXT 2001-10-22 17:01:11 +00:00
ChangeLog.pre-2-6 don't cast a PIXTEXT cell to a PIXMAP cell (fixes crash when using PIXTEXT 2001-10-22 17:01:11 +00:00
ChangeLog.pre-2-8 don't cast a PIXTEXT cell to a PIXMAP cell (fixes crash when using PIXTEXT 2001-10-22 17:01:11 +00:00
ChangeLog.pre-2-10 don't cast a PIXTEXT cell to a PIXMAP cell (fixes crash when using PIXTEXT 2001-10-22 17:01:11 +00:00
config.guess
config.h.win32.in
config.sub
configure.in
COPYING
gdk-2.0-uninstalled.pc.in
gdk-2.0.pc.in
gdk-pixbuf-2.0-uninstalled.pc.in
gdk-pixbuf-2.0.pc.in
gtk-config-2.0.in
gtk+-2.0-uninstalled.pc.in
gtk+-2.0.pc.in
gtk+.spec.in
HACKING
INSTALL
INSTALL.in
makecopyright
Makefile.am
NEWS
NEWS.pre-1-0
README
README.cvs-commits
README.in
README.nanox
README.win32
sanity_check
TODO
TODO.xml

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

This is GTK+ version 1.3.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/

Information about mailing lists can be found at
  http://www.gtk.org/mailinglists.html

Installation
============

See the file 'INSTALL'

How to report bugs
==================

Bugs should be reported to the GNOME bug tracking system. 
(http://bugzilla.gnome.org, product gtk+.) You will need
to create an account for yourself.
  
In the bug report please include:
  
* 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.

* 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 should also be submitted to bugzilla.gnome.org. If the
patch fixes an existing bug, add the patch as an attachment
to that bug report.

Otherwise, enter a new bug report that describes the patch,
and attach the patch to that bug report.

Bug reports containing patches should include the PATCH keyword
in their keyword fields. If the patch adds to or changes the GTK
programming interface, the API keyword should also be included.
  
Patches should be in unified diff form. (The -u option to GNU
diff.)