Go to file
Havoc Pennington fe9f9d03f4 New function to create a pixbuf pointing to a subregion of another pixbuf.
2000-11-01  Havoc Pennington  <hp@pobox.com>

* gdk-pixbuf.c (gdk_pixbuf_new_subpixbuf): New function to create
a pixbuf pointing to a subregion of another pixbuf.

2000-11-01  Havoc Pennington  <hp@pobox.com>

* gtk/gtklabel.c (gtk_label_set_attributes): Set a PangoAttrList
on a label
(gtk_label_finalize): unref the attr list if any.

* gtk/testgtk.c (create_get_image): close test on second click
(make_message_dialog): close dialog if it exists

* gdk/gdkpango.c (gdk_draw_layout): Handle rise attribute

* gdk-2.0.pc.in (Requires): Make it require gdk-pixbuf-2.0 not
gdk-pixbuf

* gtk/gtklabel.c (gtk_label_set_markup): new function to set label
from Pango markup format
(gtk_label_set_markup_with_accel): ditto but with accelerator
parsing

* gtk/gtkimage.c (gtk_image_expose): reformatting.

* gdk/gdkpixbuf-drawable.c (gdk_pixbuf_get_from_drawable): Hack to
reflect current state of GDK - use gdk_drawable_get_colormap, etc.
Check GDK_IS_WINDOW() not !GDK_IS_PIXMAP() to decide whether to
call gdk_window_get_origin().

* gdk/gdkpixbuf-render.c (gdk_pixbuf_render_to_drawable_alpha):
implement GDK_PIXBUF_ALPHA_FULL
2000-11-01 07:07:46 +00:00
contrib
debian
demos
docs New function to create a pixbuf pointing to a subregion of another pixbuf. 2000-11-01 07:07:46 +00:00
examples
gdk New function to create a pixbuf pointing to a subregion of another pixbuf. 2000-11-01 07:07:46 +00:00
gdk-pixbuf New function to create a pixbuf pointing to a subregion of another pixbuf. 2000-11-01 07:07:46 +00:00
gtk New function to create a pixbuf pointing to a subregion of another pixbuf. 2000-11-01 07:07:46 +00:00
m4macros
modules
po s/utf-8/UTF-8/ 2000-10-30 22:43:49 +00:00
tests New function to create a pixbuf pointing to a subregion of another pixbuf. 2000-11-01 07:07:46 +00:00
.cvsignore
acconfig.h
acinclude.m4
AUTHORS
autogen.sh
ChangeLog New function to create a pixbuf pointing to a subregion of another pixbuf. 2000-11-01 07:07:46 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-1-2
ChangeLog.pre-2-0 New function to create a pixbuf pointing to a subregion of another pixbuf. 2000-11-01 07:07:46 +00:00
ChangeLog.pre-2-2 New function to create a pixbuf pointing to a subregion of another pixbuf. 2000-11-01 07:07:46 +00:00
ChangeLog.pre-2-4 New function to create a pixbuf pointing to a subregion of another pixbuf. 2000-11-01 07:07:46 +00:00
ChangeLog.pre-2-6 New function to create a pixbuf pointing to a subregion of another pixbuf. 2000-11-01 07:07:46 +00:00
ChangeLog.pre-2-8 New function to create a pixbuf pointing to a subregion of another pixbuf. 2000-11-01 07:07:46 +00:00
ChangeLog.pre-2-10 New function to create a pixbuf pointing to a subregion of another pixbuf. 2000-11-01 07:07:46 +00:00
config.guess
config.h.win32
config.sub
configure.in
COPYING
gdk-2.0.pc.in New function to create a pixbuf pointing to a subregion of another pixbuf. 2000-11-01 07:07:46 +00:00
gdk-pixbuf-2.0.pc.in
gtk-2.0.m4
gtk-config-2.0.in
gtk-config.in
gtk+-2.0.pc.in
gtk+.spec.in
HACKING
INSTALL
INSTALL.in
ltconfig
ltmain.sh
makecopyright
Makefile.am
NEWS
NEWS.pre-1-0
README
README.cvs-commits
README.in
README.nanox
README.win32
sanity_check
TODO
TODO.xml Another test commit TODO.xml 2000-10-29 02:44:07 +00:00

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

This is GTK+ version 1.3.1. 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.3.1

[ Please substitute 1.3.1 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.3.1

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