GTK is a multi-platform toolkit for creating graphical user interfaces.
Go to file
Lars Hamann e94a7b1a7a new flags : homogeneous; new guints : tab_hborder, tab_vborder; marked
Tue Nov 17 00:06:29 1998  Lars Hamann  <lars@gtk.org>

	* gtk/gtknotebook.h (struct _GtkNotebook): new flags : homogeneous;
	new guints : tab_hborder, tab_vborder; marked tab_border deprecated
	(struct _GtkNotebookPage): new flags : expand, fill, pack

	* gtk/gtknotebook.h/c
	(gtk_notebook_set_homogeneous_tabs): new function. set homogeneneous
 	tabs
	(gtk_notebook_set_tab_border): set tab_h/vborder to tab_border
	(gtk_notebook_set_tab_hborder): new function. set tab_hborder
	(gtk_notebook_set_tab_vborder): new function. set tab_vborder
	(gtk_notebook_query_tab_label): new function. get tab_label widget.
	(gtk_notebook_set_tab_label): new function. set tab_label widget.
	(gtk_notebook_set_tab_label_text): new function. set tab_label text.
	(gtk_notebook_query_menu_label): new function. get tab_label widget.
	(gtk_notebook_set_menu_label): new function. set tab_label widget.
	(gtk_notebook_set_menu_label_text): new function. set tab_label text.
	(gtk_notebook_set_tab_label_packing): new function. set tab_label
 	fill, expand, fill_type
	(gtk_notebook_query_tab_label_packing): new function. get tab_label
 	fill, expand, fill_type

	(gtk_notebook_real_page_position): return logic page number
	(gtk_notebook_search_page) search next/prev logic page
	(gtk_notebook_update_labels): set logic page number.
	(gtk_notebook_page_compare): renamed gtk_notebook_find_page
	(gtk_notebook_set/get_child_arg): new args CHILD_ARG_TAB_EXPAND,
 	CHILD_ARG_TAB_FILL, CHILD_ARG_TAB_PACK
 	(gtk_notebook_button_press) (gtk_notebook_key_press)
 	(gtk_notebook_focus) (gtk_notebook_pages_allocate)
	(gtk_notebook_calc_tabs) (gtk_notebook_switch_focus_tab)
 	use gtk_notebook_search_page
	(gtk_notebook_page_allocate): fixed allocation bug
	(gtk_notebook_set/get_arg): new args TAB_HBORDER, TAB_VBORDER.
	(gtk_notebook_init): unset GTK_NO_WINDOW flag
	(gtk_notebook_size_request): check whether page->child is visible.
 	changes due to tab h/vborder, homogeneous tabs
	(gtk_notebook_paint): don't draw invisible tabs
	(gtk_notebook_switch_page): calculate page_num if it's less than 0
 	(gtk_notebook_append_*) (gtk_notebook_prepend_*)
 	(gtk_notebook_insert_page): removed sanity checks

	* gtk/testgtk.c (create_notebook): extended Notebook sample a bit.
1998-11-16 23:40:50 +00:00
debian
docs
examples forward declaration for gtk_window_paint declare xid_ht static get the 1998-11-07 16:12:37 +00:00
gdk New function gdk_pixmap_foreign_new(). (gtk-blizzard-981005-0. Christopher 1998-11-13 21:28:36 +00:00
gtk new flags : homogeneous; new guints : tab_hborder, tab_vborder; marked 1998-11-16 23:40:50 +00:00
tests new flags : homogeneous; new guints : tab_hborder, tab_vborder; marked 1998-11-16 23:40:50 +00:00
.cvsignore
acconfig.h
acinclude.m4
AUTHORS
autogen.sh
ChangeLog new flags : homogeneous; new guints : tab_hborder, tab_vborder; marked 1998-11-16 23:40:50 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-2-0 new flags : homogeneous; new guints : tab_hborder, tab_vborder; marked 1998-11-16 23:40:50 +00:00
ChangeLog.pre-2-2 new flags : homogeneous; new guints : tab_hborder, tab_vborder; marked 1998-11-16 23:40:50 +00:00
ChangeLog.pre-2-4 new flags : homogeneous; new guints : tab_hborder, tab_vborder; marked 1998-11-16 23:40:50 +00:00
ChangeLog.pre-2-6 new flags : homogeneous; new guints : tab_hborder, tab_vborder; marked 1998-11-16 23:40:50 +00:00
ChangeLog.pre-2-8 new flags : homogeneous; new guints : tab_hborder, tab_vborder; marked 1998-11-16 23:40:50 +00:00
ChangeLog.pre-2-10 new flags : homogeneous; new guints : tab_hborder, tab_vborder; marked 1998-11-16 23:40:50 +00:00
config.guess
config.h.in
config.sub
configure.in
COPYING
gtk-config.in
gtk.m4
gtk+.spec
HACKING
INSTALL
install-sh
ltconfig
ltmain.sh
makecopyright
Makefile.am
missing
mkinstalldirs
NEWS
NEWS.pre-1-0
README
README.cvs-commits
sanity_check
stamp-h.in
TODO

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

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