mirror of
https://gitlab.gnome.org/GNOME/gtk.git
synced 2024-12-25 13:11:13 +00:00
GTK is a multi-platform toolkit for creating graphical user interfaces.
323bcc614d
2003-06-28 Tor Lillqvist <tml@iki.fi> Fix for #111028, thanks to J. Ali Harlow, who writes: I found that the GdkPixmap->GdkImage reference really isn't important. It's only really there to have somewhere convenient to store the location of the pixel data in the pixmap and as an easy way of accessing the dimensions of that data. I have therefore put together a fix which removes this reference entirely which seems to solve the problem. * gdk/win32/gdkpixmap-win32.h (struct _GdkPixmapImplWin32): Instead of a pointer to a GdkImage, keep a pointer to the pixels directly. * gdk/win32/gdkimage-win32.c (_gdk_win32_setup_pixmap_image): Remove. (_gdk_win32_new_image): New function, replacing the above. Creates a GdkImage without any associated GdkPixmap. (gdk_image_new_bitmap, _gdk_image_new_for_depth): Use it instead. * gdk/win32/gdkprivate-win32.h: Remove from here, too. * gdk/win32/gdkcursor-win32.c (gdk_cursor_new_from_pixmap) * gdk/win32/gdkdrawable-win32.c (blit_from_pixmap) * gdk/win32/gdkgc-win32.c (_gdk_win32_bitmap_to_hrgn) * gdk/win32/gdkmain-win32.c (_gdk_win32_drawable_description): * gdk/win32/gdkpixmap-win32.c (gdk_pixmap_impl_win32_finalize, gdk_pixmap_new, gdk_bitmap_create_from_data, gdk_pixmap_foreign_new) Corresponding changes. |
||
---|---|---|
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.h.win32.in | ||
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-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.win32 | ||
sanitize-la.sh | ||
sanity_check |
General Information =================== This is GTK+ version 2.3.0. GTK+ is a multi-platform toolkit for creating graphical user interfaces. Offering a complete set of widgets, GTK+ is suitable for projects ranging from small one-off projects to complete application suites. GTK+ is free software and part of the GNU Project. However, the licensing terms for GTK+, the GNU LGPL, allow it to be used by all developers, including those developing proprietary software, without any license fees or royalties. 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' Release notes ============= * As compared to GTK+-1.2, the default configuration of GTK+-2 has been stream-lined to reduce confusion on the part of new users or users coming from other environments. Users used to older versions of GTK+ may want to make some adjustments to the default configuration. - Emacs keybindings such as Control-A and Control-E to move to the ends of lines are not enabled by default in the editing widgets. To turn on Emacs keybindings, add the line: gtk-key-theme-name = "Emacs" To your ~/.gtkrc-2.0 - Editing of menu accelerators by pressing an accelerator over the menu item is disabled by default. To enable, it, add: gtk-can-change-accels = 1 to your ~/.gtkrc-2.0 - To improve useability for keyboard operation, GTK+ now selects the contents of an entry when tabbing into it or when it is focused on initial window map. To disable this behavior, add: gtk-entry-select-on-focus = 0 to your ~/.gtkrc-2.0 * The GTK+ libraries use an '_' prefix to indicate private symbols that must not be used by applications. On some platforms, symbols beginning with prefixes such as _gtk, _gdk, and _pango will be exported from the library, on others not. In no case can applications use these private symbols. * GTK+-2.2 can be build either with Pango-1.0 and version 1 of the Xft library or Pango-1.2 and version 2 of the Xft library (Xft is used to to display anti-aliased fonts) By default, GTK+ and Pango are built so that applications will not have explicit dependencies on either version of Xft. To make sure that your application will be binary compatible with future versions of GTK+: - Do not configure Pango or GTK+ with the --enable-static or --enable-explicit-deps options, since they will cause dependencies on the particular version of Xft. - Do not use Xft version 1 directly in your applications. * There is a bug in the Xft library in XFree86-4.1 and possibly previous versions that causes random crashes when using the Pango Xft backend. If you want to use Xft fonts, you should upgrade to XFree86-4.2. * Xft support is on by default when using Xft2 but off by default when using Xft1. To change this default, set the variable GDK_USE_XFT to '1' or '0'. For instance, to turn on Xft fonts when Xft1. GDK_USE_XFT=1 export GDK_USE_XFT * The gdk_pixbuf_xlib library included in the contrib/ directory of GTK+ is provided on a as-is basis and has not been tested at all. No guarantees about the degree of workingness or about future compatibility are provided. * While efforts have been made to make gdk-pixbuf robust against invalid images, using gdk-pixbuf to load untrusted data is not recommended, due to the likelyhood that there are additional problems where an invalid image could cause gdk-pixbuf to crash or worse. * The assumption of GLib and GTK+ by default is that filenames on the filesystem are encoded in UTF-8 rather than the encoding of the locale; The GTK+ developers consider that having filenames whose interpretation depends on the current locale is fundamentally a bad idea. If you have filenames encoded in the encoding of your locale, then you may want to set the G_BROKEN_FILENAMES environment variable: G_BROKEN_FILENAMES=1 export G_BROKEN_FILENAMES Best integration of GTK+-2.2 with the environment is achieved by using a UTF-8 locale. 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.)