Go to file
Hans Breuer 6ff97d2e0b disable USE_MMX for msvc build cause the assembler doesn't fit and is out
2001-03-31  Hans Breuer  <hans@breuer.org>

	* config.h.win32.in : disable USE_MMX for msvc build cause
	the assembler doesn't fit and is out of my scope. Disable
	USE_GMODULE for msvc build as wel. The right way to share
	binaries on win32 would be to use libtiff.dll etc. To reduce
	installation hassles IMO it's better to include all fileformats
	builtin to gdk-pixbuf

	* gdk-pixbuf/makefile.msc : new file

	* gdk/gdk.def : updated

	* gdk/win32/gdkevents-win32.c : don't erase the background if
	.no_bg is set. It improves the scrolling (e.g. of testgtk main
	buttons
	* gdk/win32/gdkgeometry-win32.c : added comment about the above

	* gdk/win32/gdkwindow-win32.c : added three new functions like
	the X version. Only one is implemented, because the other two
	"gdk_window_begin_(resize|move)_drag" got no docs and appear to
	be default behaviour on win32 anyway ...

	* gtk/gtk.def : updated

	* gtk/makefile.msc.in : update for new files, use glib-genmarshal
	from where it was built and add an additional rule to automagically
	build gtkmarshal.[hc]

	* gtk/gtkfilesel.c (open_new_dir) : don't increase n_entries
	before array access for the current entry isn't finished

	* gtk/gtktreeitem.c (gtk_tree_item_subtree_button_click) :
	use g_return_val_if_fail

	* gtk/testgtk.c (window_controls) : don't use the *wrong* size
	for the static array, but let the compiler calculate it. It
	makes me wonder if gcc isn't capable to catch bugs like this ...
2001-03-31 19:33:49 +00:00
contrib Commit missed changelog entry bit. 2001-01-17 19:32:55 +00:00
debian
demos handle mnemonics in the stock item label 2001-03-22 06:45:57 +00:00
docs added value_changed signal which proxies for the adjustment. Cleaned 2001-03-30 03:35:47 +00:00
examples Make gdk_colormap_sync private since it was never exported in a header 2001-02-02 22:19:31 +00:00
gdk disable USE_MMX for msvc build cause the assembler doesn't fit and is out 2001-03-31 19:33:49 +00:00
gdk-pixbuf disable USE_MMX for msvc build cause the assembler doesn't fit and is out 2001-03-31 19:33:49 +00:00
gtk disable USE_MMX for msvc build cause the assembler doesn't fit and is out 2001-03-31 19:33:49 +00:00
m4macros
modules rename set_cursor_pos to set_cursor_location in GtkInputContext class 2001-03-16 01:44:54 +00:00
po Utf-8'ification 2001-03-17 11:52:12 +00:00
tests added value_changed signal which proxies for the adjustment. Cleaned 2001-03-30 03:35:47 +00:00
.cvsignore shut up CVS 2001-03-05 19:56:46 +00:00
acconfig.h
acinclude.m4
AUTHORS
autogen.sh
ChangeLog disable USE_MMX for msvc build cause the assembler doesn't fit and is out 2001-03-31 19:33:49 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-1-2
ChangeLog.pre-2-0 disable USE_MMX for msvc build cause the assembler doesn't fit and is out 2001-03-31 19:33:49 +00:00
ChangeLog.pre-2-2 disable USE_MMX for msvc build cause the assembler doesn't fit and is out 2001-03-31 19:33:49 +00:00
ChangeLog.pre-2-4 disable USE_MMX for msvc build cause the assembler doesn't fit and is out 2001-03-31 19:33:49 +00:00
ChangeLog.pre-2-6 disable USE_MMX for msvc build cause the assembler doesn't fit and is out 2001-03-31 19:33:49 +00:00
ChangeLog.pre-2-8 disable USE_MMX for msvc build cause the assembler doesn't fit and is out 2001-03-31 19:33:49 +00:00
ChangeLog.pre-2-10 disable USE_MMX for msvc build cause the assembler doesn't fit and is out 2001-03-31 19:33:49 +00:00
config.guess
config.h.win32.in disable USE_MMX for msvc build cause the assembler doesn't fit and is out 2001-03-31 19:33:49 +00:00
config.sub
configure.in Delete. 2001-03-15 19:02:23 +00:00
COPYING
gdk-2.0.pc.in
gdk-pixbuf-2.0.pc.in Remove spurious const. 2001-03-03 18:39:33 +00:00
gtk-2.0.m4
gtk-config-2.0.in
gtk+-2.0.pc.in Remove spurious const. 2001-03-03 18:39:33 +00:00
gtk+.spec.in
HACKING
INSTALL
INSTALL.in
ltconfig
ltmain.sh
makecopyright
Makefile.am use full set, since current set wasn't building on all configs. 2001-03-08 01:33:01 +00:00
NEWS
NEWS.pre-1-0
README
README.cvs-commits
README.in
README.nanox
README.win32 Update. Mention the gtk-1-3-win32-production branch. 2001-02-23 03:51:41 +00:00
sanity_check
TODO
TODO.xml

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

This is GTK+ version 1.3.2. 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.2

[ Please substitute 1.3.2 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.2

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