callisto-debian/gtk3
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
4,152 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%
4e8cbdca6b
Go to file
Havoc Pennington 4e8cbdca6b don't create layout if we didn't have one (gtk_text_view_set_buffer): 
2001-10-24  Havoc Pennington  <hp@redhat.com>

	* gtk/gtktextview.c (gtk_text_view_update_adjustments): don't
	create layout if we didn't have one
	(gtk_text_view_set_buffer): invalidate so we get the idle handlers
	as appropriate, avoids blanking the screen
	(gtk_text_view_invalidate): new function to do invalidation,
	containing old guts of invalidated_handler
2001-10-24 16:11:41 +00:00
contrib
debian
demos Remove handle_box from App demo. 2001-10-22 18:24:29 +00:00
docs if we move to the front of a segment, use the "slow" technique for moving 2001-10-24 04:48:21 +00:00
examples
gdk Always set window->parent (except or the root window itself); if the 2001-10-24 14:15:50 +00:00
gdk-pixbuf
gtk don't create layout if we didn't have one (gtk_text_view_set_buffer): 2001-10-24 16:11:41 +00:00
m4macros
modules
po More updates. 2001-10-24 12:12:10 +00:00
tests if we move to the front of a segment, use the "slow" technique for moving 2001-10-24 04:48:21 +00:00
.cvsignore correct docs for use_align 2001-10-19 20:46:43 +00:00
acconfig.h
acinclude.m4
AUTHORS
autogen.sh
ChangeLog don't create layout if we didn't have one (gtk_text_view_set_buffer): 2001-10-24 16:11:41 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-1-2
ChangeLog.pre-2-0 don't create layout if we didn't have one (gtk_text_view_set_buffer): 2001-10-24 16:11:41 +00:00
ChangeLog.pre-2-2 don't create layout if we didn't have one (gtk_text_view_set_buffer): 2001-10-24 16:11:41 +00:00
ChangeLog.pre-2-4 don't create layout if we didn't have one (gtk_text_view_set_buffer): 2001-10-24 16:11:41 +00:00
ChangeLog.pre-2-6 don't create layout if we didn't have one (gtk_text_view_set_buffer): 2001-10-24 16:11:41 +00:00
ChangeLog.pre-2-8 don't create layout if we didn't have one (gtk_text_view_set_buffer): 2001-10-24 16:11:41 +00:00
ChangeLog.pre-2-10 don't create layout if we didn't have one (gtk_text_view_set_buffer): 2001-10-24 16:11:41 +00:00
config.guess
config.h.win32.in
config.sub
configure.in
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+-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.9. 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.)