mirror of
https://gitlab.gnome.org/GNOME/gtk.git
synced 2024-09-20 14:00:10 +00:00
GTK is a multi-platform toolkit for creating graphical user interfaces.
3eb0ecf480
2001-01-06 Hans Breuer <hans@breuer.org> * gdk/gdk.def : updated exports * gdk/win32/makefile.msc : -DGDK_ENABLE_BROKEN otherwise gdk won't compile anymore * gdk/win32/gdkevents-win32.c : initialize ret_val when processing GDK_FILTER functions, initialize event.key->hardware_keycode. Improved gdk_flush () to not only do pending drawing operations but also process all currently pending events. This should make the behaviour more similar to the X11 version. * gdk/win32/gdkgc-win32.c (predraw_set_background) : a background option needs to be set even if there is no GDK_GC_BACKGROUND. (gdk_win32_hdc_get) : use predraw_set_background () independent of value_mask. This allows to draw dashed lines leaving the original background intact. * gdk/win32/gdkimage-win32.c (gdk_image_new_bitamp) : free data after processing, because we can't reuse it as the X11 version does. * gtk/gtk.def : updated exports * gtk/makefile.msc.in : added ATK, removed all test apps. (I would like to get rid of this file again, and use straight makefile.msc again, as the other Gtk+ subdirs do) * test/makefile.msc (new file) : build the test apps here (phase two: something has send me a broken pipe signal :) |
||
|---|---|---|
| contrib | ||
| debian | ||
| demos | ||
| docs | ||
| examples | ||
| gdk | ||
| gdk-pixbuf | ||
| gtk | ||
| m4macros | ||
| modules | ||
| po | ||
| tests | ||
| .cvsignore | ||
| acconfig.h | ||
| acinclude.m4 | ||
| AUTHORS | ||
| autogen.sh | ||
| ChangeLog | ||
| ChangeLog.pre-1-0 | ||
| ChangeLog.pre-1-2 | ||
| ChangeLog.pre-2-0 | ||
| ChangeLog.pre-2-2 | ||
| ChangeLog.pre-2-4 | ||
| ChangeLog.pre-2-6 | ||
| ChangeLog.pre-2-8 | ||
| ChangeLog.pre-2-10 | ||
| config.guess | ||
| config.h.win32.in | ||
| config.sub | ||
| configure.in | ||
| COPYING | ||
| gdk-2.0.pc.in | ||
| gdk-pixbuf-2.0.pc.in | ||
| gtk-2.0.m4 | ||
| gtk-config-2.0.in | ||
| gtk+-2.0.pc.in | ||
| gtk+.spec.in | ||
| HACKING | ||
| INSTALL | ||
| INSTALL.in | ||
| ltconfig | ||
| ltmain.sh | ||
| makecopyright | ||
| Makefile.am | ||
| NEWS | ||
| NEWS.pre-1-0 | ||
| README | ||
| README.cvs-commits | ||
| README.in | ||
| README.nanox | ||
| README.win32 | ||
| sanity_check | ||
| TODO | ||
| TODO.xml | ||
General Information =================== This is GTK+ version 1.3.5. 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.)