callisto-debian/gtk3
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
5,107 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%
8beceb3846
Go to file
Tor Lillqvist 8beceb3846 Remove the event_mask, it is now in GdkWindowObject. 
2002-03-01  Tor Lillqvist  <tml@iki.fi>

	* gdk/win32/gdkwindow-win32.h (struct _GdkWindowImplWin32): Remove
	the event_mask, it is now in GdkWindowObject.

	* gdk/win32/gdkwindow-win32.c: Change accordingly. Set the
	GDK_STRUCTURE_MASK in gdk_window_set_events(), as it is always set
	in gdk_window_new(), too. (Bug#72921)

	* gdk/win32/gdkevents-win32.c: Change accordingly here, too.
	(vk_from_char): New function, calculates the virtual keycode
	corresponding to the char in a WM_CHAR message.
	(build_keypress_event, build_keyrelease_event): Use it.
	(build_keypress_event): Call ImmReleaseContext() after using the
	input context. This might plug a memory or resource leak.
	(build_key_event_state): Remove #if 0 code.
	(gdk_event_translate): Actually, it would be preferrable to always
	handle just the WM_KEYDOWN and WM_KEYUP messages, not WM_CHAR at
	all, and thus drop the contorted logic with ignore_wm_char etc.

	* gdk/win32/gdkkeys-win32.c: (gdk_keymap_get_entries_for_keyval):
	Debugging output.
	(gdk_keymap_translate_keyboard_state): Return correct value. (But
	_gtk_key_hash_lookup() doesn't check the return value...)
2002-02-28 23:38:55 +00:00
contrib
debian
demos
docs
examples
gdk Remove the event_mask, it is now in GdkWindowObject. 2002-02-28 23:38:55 +00:00
gdk-pixbuf Move the call to correct_total() to the right spot. (#72732) 2002-02-28 18:47:38 +00:00
gtk Allow focus-change events to be sent to unrealized widgets; they aren't 2002-02-27 23:53:29 +00:00
m4macros
modules Add ko and zh to the locales where this is the default. 2002-02-27 19:09:35 +00:00
po Updated Slovenian translation 2002-02-28 23:35:45 +00:00
tests
.cvsignore
acconfig.h
acinclude.m4
AUTHORS
autogen.sh
ChangeLog Remove the event_mask, it is now in GdkWindowObject. 2002-02-28 23:38:55 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-1-2
ChangeLog.pre-2-0 Remove the event_mask, it is now in GdkWindowObject. 2002-02-28 23:38:55 +00:00
ChangeLog.pre-2-2 Remove the event_mask, it is now in GdkWindowObject. 2002-02-28 23:38:55 +00:00
ChangeLog.pre-2-4 Remove the event_mask, it is now in GdkWindowObject. 2002-02-28 23:38:55 +00:00
ChangeLog.pre-2-6 Remove the event_mask, it is now in GdkWindowObject. 2002-02-28 23:38:55 +00:00
ChangeLog.pre-2-8 Remove the event_mask, it is now in GdkWindowObject. 2002-02-28 23:38:55 +00:00
ChangeLog.pre-2-10 Remove the event_mask, it is now in GdkWindowObject. 2002-02-28 23:38:55 +00:00
config.h.win32.in
configure.in beautified configure --help output. 2002-02-28 10:15:55 +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.15. 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.)