callisto-debian/gtk2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
1,654 Commits 2 Branches 0 Tags 169 MiB
C 90.2%
Makefile 7.8%
Shell 1.4%
M4 0.3%
Python 0.2%
fea53a95f8
Go to file
Owen Taylor fea53a95f8 Set and read the XdndActionList property defined in the Xdnd spec. We do 
Thu Jan 21 02:11:44 1999  Owen Taylor  <otaylor@redhat.com>

	* Set and read the XdndActionList property defined
	in the Xdnd spec. We do this always, not just for
	XdndActionAsk like the spec says, but if we don't
	find it, we fall back to actions = suggested_action,
	which is compatible with the language of the spec.
1999-01-21 07:08:25 +00:00
debian
docs Some editing, a little more detail. 1999-01-18 19:27:43 +00:00
examples
gdk Set and read the XdndActionList property defined in the Xdnd spec. We do 1999-01-21 07:08:25 +00:00
gdk-pixbuf
gtk Default handling for drops should be keyed on GTK_DRAG_DEFAULT_DROP not 1999-01-21 05:59:04 +00:00
po First draft of the Russian translations. 1999-01-18 05:45:41 +00:00
tests deprecated gtk_check_menu_item_set_state, people should use 1999-01-17 14:52:22 +00:00
.cvsignore
acconfig.h
acinclude.m4 Unset CATOBJEXT so that the macros and Makefiles correctly handle 1999-01-14 02:16:49 +00:00
AUTHORS
autogen.sh
ChangeLog Set and read the XdndActionList property defined in the Xdnd spec. We do 1999-01-21 07:08:25 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-2-0 Set and read the XdndActionList property defined in the Xdnd spec. We do 1999-01-21 07:08:25 +00:00
ChangeLog.pre-2-2 Set and read the XdndActionList property defined in the Xdnd spec. We do 1999-01-21 07:08:25 +00:00
ChangeLog.pre-2-4 Set and read the XdndActionList property defined in the Xdnd spec. We do 1999-01-21 07:08:25 +00:00
ChangeLog.pre-2-6 Set and read the XdndActionList property defined in the Xdnd spec. We do 1999-01-21 07:08:25 +00:00
ChangeLog.pre-2-8 Set and read the XdndActionList property defined in the Xdnd spec. We do 1999-01-21 07:08:25 +00:00
ChangeLog.pre-2-10 Set and read the XdndActionList property defined in the Xdnd spec. We do 1999-01-21 07:08:25 +00:00
config.guess
config.sub
configure.in New variable. Define to $prefix/$DATADIRNAME/locale. This will point to 1999-01-20 23:43:08 +00:00
COPYING
gtk-config.in
gtk.m4
gtk+.spec Update to version 1.1.3, change packager address. 1999-01-17 16:25:20 +00:00
HACKING - GNU autoconf 2.13 - GNU automake 1.4 (Beta releases are at 1999-01-17 16:54:58 +00:00
INSTALL Released GTK+ 1.1.13 1999-01-18 00:27:59 +00:00
install-sh
ltconfig
ltmain.sh
makecopyright
Makefile.am
missing
mkinstalldirs
NEWS removed deprecated functions: gtk_clist_set_border, 1999-01-17 23:12:18 +00:00
NEWS.pre-1-0
README Released GTK+ 1.1.13 1999-01-18 00:27:59 +00:00
README.cvs-commits
sanity_check
stamp-h.in
TODO

README 

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

This is GTK+ version 1.1.13.   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".