callisto-debian/gtk3
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
4,656 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%
815ffe2edd
Go to file
Owen Taylor 815ffe2edd Stop the timer on destroy, or when we are notified that we are shadowed by 
Tue Jan 15 18:10:24 2002  Owen Taylor  <otaylor@redhat.com>

	* gtk/gtkspinbutton.c (gtk_spin_button_grab_notify): Stop
	the timer on destroy, or when we are notified that we are
	shadowed by a modal dialog.

	* gtk/gtkspinbutton.c: Remove explicit gtk_grab_add()/remove() -
	not needed any more.

	* gtk/gtkmain.c (gtk_grab_notify): Fix problem where notifications
	weren't sent out for the default grab group.

	* gtk/gtkmain.c (gtk_grab_notify): Fix notification of widgets that
	were getting events because they were part of the previous grab.
2002-01-16 01:07:11 +00:00
contrib
debian
demos
docs map event_window after mapping child, so we don't loose events. 2002-01-15 13:24:03 +00:00
examples
gdk Don't mangle sequences of consecutive \n or \r. 2002-01-14 23:11:35 +00:00
gdk-pixbuf Credit Michael Hore for last two changes 2002-01-12 00:26:25 +00:00
gtk Stop the timer on destroy, or when we are notified that we are shadowed by 2002-01-16 01:07:11 +00:00
m4macros
modules
po Added ms at ALL_LINGUAS. Added Malay Translation. But not all translated 2002-01-14 01:39:24 +00:00
tests allow cancel to happen. 2002-01-14 22:00:26 +00:00
.cvsignore
acconfig.h
acinclude.m4
AUTHORS
autogen.sh
ChangeLog Stop the timer on destroy, or when we are notified that we are shadowed by 2002-01-16 01:07:11 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-1-2
ChangeLog.pre-2-0 Stop the timer on destroy, or when we are notified that we are shadowed by 2002-01-16 01:07:11 +00:00
ChangeLog.pre-2-2 Stop the timer on destroy, or when we are notified that we are shadowed by 2002-01-16 01:07:11 +00:00
ChangeLog.pre-2-4 Stop the timer on destroy, or when we are notified that we are shadowed by 2002-01-16 01:07:11 +00:00
ChangeLog.pre-2-6 Stop the timer on destroy, or when we are notified that we are shadowed by 2002-01-16 01:07:11 +00:00
ChangeLog.pre-2-8 Stop the timer on destroy, or when we are notified that we are shadowed by 2002-01-16 01:07:11 +00:00
ChangeLog.pre-2-10 Stop the timer on destroy, or when we are notified that we are shadowed by 2002-01-16 01:07:11 +00:00
config.guess
config.h.win32.in
config.sub
configure.in Added ms at ALL_LINGUAS. Added Malay Translation. But not all translated 2002-01-14 01:39:24 +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.12. 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.)