callisto-debian/gtk3
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
2,351 Commits 3 Branches 0 Tags 363 MiB
C 88.6%
CSS 10.1%
Meson 0.4%
SCSS 0.4%
JavaScript 0.2%
Other 0.1%
51a0dc303d
Go to file
Federico Mena Quintero 51a0dc303d Removed debugging g_print. Thanks to John Sullivan <sullivan@eazel.com> 
2000-02-02  Federico Mena Quintero  <federico@helixcode.com>

	* gdk-pixbuf/io-gif.c (gif_get_lzw): Removed debugging g_print.
	Thanks to John Sullivan <sullivan@eazel.com> for the patch.

	* gdk-pixbuf/testpixbuf-drawable.c (configure_cb): Get a new area
	of the screen when the window is resized.  Thanks to David
	N. Welton <davidw@linuxcare.com> for pointing this out.
	Misc. cleanups to the rest of the file.
2000-02-02 05:47:57 +00:00
debian Argh. Missed one dumb space in rules file. Fixed. 1998-11-18 06:25:35 +00:00
demos Removed debugging g_print. Thanks to John Sullivan <sullivan@eazel.com> 2000-02-02 05:47:57 +00:00
docs rearranged a bit. 2000-02-02 03:23:11 +00:00
examples Adapt cast macros to standard. 1999-11-22 21:52:50 +00:00
gdk forgot to cvs add this 2000-01-29 22:27:09 +00:00
gdk-pixbuf Removed debugging g_print. Thanks to John Sullivan <sullivan@eazel.com> 2000-02-02 05:47:57 +00:00
gtk Add some sanity checks if the widget passed to gtk_drag_get_data() was not 2000-02-01 19:05:18 +00:00
po Handle zh_CN.GB2312. 2000-01-31 20:13:14 +00:00
tests use gdk_cursor_unref instead of destroy 2000-01-29 22:26:41 +00:00
.cvsignore .cvsignore additions 2000-01-21 21:57:14 +00:00
acconfig.h
acinclude.m4
AUTHORS
autogen.sh
ChangeLog Add some sanity checks if the widget passed to gtk_drag_get_data() was not 2000-02-01 19:05:18 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-1-2
ChangeLog.pre-2-0 Add some sanity checks if the widget passed to gtk_drag_get_data() was not 2000-02-01 19:05:18 +00:00
ChangeLog.pre-2-2 Add some sanity checks if the widget passed to gtk_drag_get_data() was not 2000-02-01 19:05:18 +00:00
ChangeLog.pre-2-4 Add some sanity checks if the widget passed to gtk_drag_get_data() was not 2000-02-01 19:05:18 +00:00
ChangeLog.pre-2-6 Add some sanity checks if the widget passed to gtk_drag_get_data() was not 2000-02-01 19:05:18 +00:00
ChangeLog.pre-2-8 Add some sanity checks if the widget passed to gtk_drag_get_data() was not 2000-02-01 19:05:18 +00:00
ChangeLog.pre-2-10 Add some sanity checks if the widget passed to gtk_drag_get_data() was not 2000-02-01 19:05:18 +00:00
config.guess
config.h.win32 Don't define HAVE_DIMM_H if MSC, as you have to get the Platform SDK to 1999-11-04 23:42:51 +00:00
config.sub
configure.in Added po file from TurboLinux Chinese Develop Team. 2000-01-30 12:21:05 +00:00
COPYING
gtk-config.in Adapt cast macros to standard. 1999-11-22 21:52:50 +00:00
gtk.m4
gtk+.spec.in Added lib/gtk+/include/* to %files (bug #5178 - Peter Wainright) 2000-01-24 01:38:17 +00:00
HACKING
INSTALL
INSTALL.in Adapt cast macros to standard. 1999-11-22 21:52:50 +00:00
ltconfig
ltmain.sh
makecopyright
Makefile.am Distribute README.win32. 1999-12-11 23:18:12 +00:00
NEWS Adapt cast macros to standard. 1999-11-22 21:52:50 +00:00
NEWS.pre-1-0
README
README.cvs-commits
README.in Adapt cast macros to standard. 1999-11-22 21:52:50 +00:00
README.win32 Distribute README.win32. 1999-12-11 23:18:12 +00:00
sanity_check
TODO

README 

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

This is GTK+ version 1.2.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
==================

Bugs should be reported to the GNOME bug tracking
system. (http://bugs.gnome.org). To report a problem
about GTK+, send mail to submit@bugs.gnome.org.

The subject of the mail should describe your problem.
In the body of the mail, you should first include
a "pseudo-header" that gives the package and 
version number. This should be separated by a blank
line from the actual headers.

 Package: gtk+
 Version: 1.2.0

[ Please substitute 1.2.0 with the version of GTK+ that
  you have installed ]

Then describe the bug. 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.

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

An example of a bug report:

====
To: submit@bugs.gnome.org
From: yourname@your.address.org
Subject: handlebox test in testgtk is misnamed.

Package: gtk+
Version: 1.2.0

When I run gtk/testgtk, the button "handle box"
is misnamed. There are multiple handle boxes in
the demo, so it should be "handle boxes", to
be like "buttons" or "check buttons".
===

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