callisto-debian/gtk3
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
4,242 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%
a1fe2ac180
Go to file
Owen Taylor a1fe2ac180 Add: - A ::retrieve_surrounding signal that asks the widget for context 
Thu Nov  1 16:20:56 2001  Owen Taylor  <otaylor@redhat.com>

	* gtk/gtkimcontext.[ch]: Add:
	  - A ::retrieve_surrounding signal that asks the widget for
	    context around the insertion point.
	  - A ::delete_surrounding signal that asks the widget to
	    delete context aroudn the insertion point.
	  - gtk_im_context_set_context() for widgets to set context
	    around the insertion point in response to ::retrieve_context.
	  - gtk_im_context_get_context() for context to get context
	    around the insertion point

	* gtkmarshal.list: Add BOOL:INT,INT

	* gtk/gtkimmulticontext.c: Proxy the get_surrounding() /
	set_surrounding() methods, and the ::retrieve_surrounding /
	::delete_surrounding signals.

	* gtk/gtkentry.c gtk/gtktreeview.c: Hook up to the
	GtkIMContext::retrieve_surrounding / ::delete_surrounding
	signals.
2001-11-01 21:50:58 +00:00
contrib
debian
demos
docs fix infinite loop noticed by yosh. 2001-11-01 00:06:32 +00:00
examples
gdk these should be 31, not 3. Hooray for Xatoms (and not using the XA_* 2001-10-31 21:52:29 +00:00
gdk-pixbuf
gtk Add: - A ::retrieve_surrounding signal that asks the widget for context 2001-11-01 21:50:58 +00:00
m4macros Don't try to use pkg-config when we didn't find it. (#62944, Eric Lemings) 2001-10-29 16:51:37 +00:00
modules
po
tests don't know why this didn't commit 2001-10-31 22:57:51 +00:00
.cvsignore shut up CVS 2001-10-30 16:51:39 +00:00
acconfig.h Don't use AC_CHECK_FILE to check for a file since it always spits warnings 2001-10-29 17:25:40 +00:00
acinclude.m4
AUTHORS
autogen.sh
ChangeLog Add: - A ::retrieve_surrounding signal that asks the widget for context 2001-11-01 21:50:58 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-1-2
ChangeLog.pre-2-0 Add: - A ::retrieve_surrounding signal that asks the widget for context 2001-11-01 21:50:58 +00:00
ChangeLog.pre-2-2 Add: - A ::retrieve_surrounding signal that asks the widget for context 2001-11-01 21:50:58 +00:00
ChangeLog.pre-2-4 Add: - A ::retrieve_surrounding signal that asks the widget for context 2001-11-01 21:50:58 +00:00
ChangeLog.pre-2-6 Add: - A ::retrieve_surrounding signal that asks the widget for context 2001-11-01 21:50:58 +00:00
ChangeLog.pre-2-8 Add: - A ::retrieve_surrounding signal that asks the widget for context 2001-11-01 21:50:58 +00:00
ChangeLog.pre-2-10 Add: - A ::retrieve_surrounding signal that asks the widget for context 2001-11-01 21:50:58 +00:00
config.guess
config.h.win32.in
config.sub
configure.in use GLIB_AC_DIVERT_BEFORE_HELP() so we get proper output for configure 2001-10-30 15:52:09 +00:00
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-zip.sh.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

README 

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

This is GTK+ version 1.3.10. 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.)