2000-12-14 23:14:18 +00:00
|
|
|
/* GDK - The GIMP Drawing Kit
|
|
|
|
* Copyright (C) 2000 Red Hat, Inc.
|
|
|
|
*
|
|
|
|
* This library is free software; you can redistribute it and/or
|
|
|
|
* modify it under the terms of the GNU Lesser General Public
|
|
|
|
* License as published by the Free Software Foundation; either
|
|
|
|
* version 2 of the License, or (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This library is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
* Lesser General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU Lesser General Public
|
|
|
|
* License along with this library; if not, write to the
|
|
|
|
* Free Software Foundation, Inc., 59 Temple Place - Suite 330,
|
|
|
|
* Boston, MA 02111-1307, USA.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Modified by the GTK+ Team and others 1997-2000. See the AUTHORS
|
|
|
|
* file for a list of people on the GTK+ Team. See the ChangeLog
|
|
|
|
* files for a list of changes. These files are distributed with
|
|
|
|
* GTK+ at ftp://ftp.gtk.org/pub/gtk/.
|
|
|
|
*/
|
|
|
|
#include <ctype.h>
|
|
|
|
#include <stdio.h>
|
|
|
|
#include <stdlib.h>
|
|
|
|
#include <string.h>
|
|
|
|
#include <limits.h>
|
|
|
|
#include <errno.h>
|
|
|
|
|
|
|
|
#include "gdk.h"
|
|
|
|
|
|
|
|
#include "gdkprivate-win32.h"
|
|
|
|
#include "gdkinternals.h"
|
|
|
|
#include "gdkkeysyms.h"
|
|
|
|
|
|
|
|
#include "config.h"
|
|
|
|
|
|
|
|
guint _gdk_keymap_serial = 0;
|
|
|
|
|
2001-06-22 14:08:51 +00:00
|
|
|
static GdkKeymap *default_keymap = NULL;
|
|
|
|
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
static guint *keysym_tab = NULL;
|
|
|
|
|
2002-09-11 21:55:48 +00:00
|
|
|
#ifdef G_ENABLE_DEBUG
|
|
|
|
static void
|
|
|
|
print_keysym_tab (void)
|
|
|
|
{
|
|
|
|
gint vk;
|
|
|
|
|
|
|
|
g_print ("keymap:\n");
|
|
|
|
for (vk = 0; vk < 256; vk++)
|
|
|
|
{
|
|
|
|
gint state;
|
|
|
|
|
|
|
|
g_print ("%#.02x: ", vk);
|
|
|
|
for (state = 0; state < 4; state++)
|
|
|
|
{
|
|
|
|
gchar *name = gdk_keyval_name (keysym_tab[vk*4 + state]);
|
|
|
|
if (name == NULL)
|
|
|
|
name = "(none)";
|
|
|
|
g_print ("%s ", name);
|
|
|
|
}
|
|
|
|
g_print ("\n");
|
|
|
|
}
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
static void
|
|
|
|
update_keymap (void)
|
|
|
|
{
|
|
|
|
static guint current_serial = 0;
|
|
|
|
guchar key_state[256];
|
|
|
|
guint scancode;
|
|
|
|
guint vk;
|
|
|
|
|
|
|
|
if (keysym_tab != NULL && current_serial == _gdk_keymap_serial)
|
|
|
|
return;
|
|
|
|
|
|
|
|
current_serial = _gdk_keymap_serial;
|
|
|
|
|
|
|
|
if (keysym_tab == NULL)
|
|
|
|
keysym_tab = g_new (guint, 4*256);
|
|
|
|
|
|
|
|
memset (key_state, 0, sizeof (key_state));
|
|
|
|
|
|
|
|
for (vk = 0; vk < 256; vk++)
|
|
|
|
{
|
|
|
|
if ((scancode = MapVirtualKey (vk, 0)) == 0)
|
|
|
|
keysym_tab[vk*4+0] =
|
|
|
|
keysym_tab[vk*4+1] =
|
|
|
|
keysym_tab[vk*4+2] =
|
|
|
|
keysym_tab[vk*4+3] = GDK_VoidSymbol;
|
|
|
|
else
|
|
|
|
{
|
|
|
|
gint i, k;
|
|
|
|
|
|
|
|
key_state[vk] = 0x80;
|
|
|
|
for (i = 0; i < 4; i++)
|
|
|
|
{
|
|
|
|
guint *ksymp = keysym_tab + vk*4 + i;
|
|
|
|
guchar chars[2];
|
|
|
|
|
|
|
|
switch (i)
|
|
|
|
{
|
|
|
|
case 0:
|
|
|
|
key_state[VK_SHIFT] = 0;
|
|
|
|
key_state[VK_CONTROL] = key_state[VK_MENU] = 0;
|
|
|
|
break;
|
|
|
|
case 1:
|
|
|
|
key_state[VK_SHIFT] = 0x80;
|
|
|
|
key_state[VK_CONTROL] = key_state[VK_MENU] = 0;
|
|
|
|
break;
|
|
|
|
case 2:
|
|
|
|
key_state[VK_SHIFT] = 0;
|
|
|
|
key_state[VK_CONTROL] = key_state[VK_MENU] = 0x80;
|
|
|
|
break;
|
|
|
|
case 3:
|
|
|
|
key_state[VK_SHIFT] = 0x80;
|
|
|
|
key_state[VK_CONTROL] = key_state[VK_MENU] = 0x80;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
*ksymp = 0;
|
|
|
|
|
|
|
|
/* First, handle those virtual keys that we always want
|
|
|
|
* as special GDK_* keysyms, even if ToAsciiEx might
|
|
|
|
* turn some them into a ASCII character (like TAB and
|
|
|
|
* ESC).
|
|
|
|
*/
|
|
|
|
switch (vk)
|
|
|
|
{
|
|
|
|
case VK_CANCEL:
|
|
|
|
*ksymp = GDK_Cancel; break;
|
|
|
|
case VK_BACK:
|
|
|
|
*ksymp = GDK_BackSpace; break;
|
|
|
|
case VK_TAB:
|
2002-03-06 00:36:08 +00:00
|
|
|
if (i & 1)
|
|
|
|
*ksymp = GDK_ISO_Left_Tab;
|
|
|
|
else
|
|
|
|
*ksymp = GDK_Tab;
|
|
|
|
break;
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
case VK_CLEAR:
|
|
|
|
*ksymp = GDK_Clear; break;
|
|
|
|
case VK_RETURN:
|
|
|
|
*ksymp = GDK_Return; break;
|
|
|
|
case VK_SHIFT:
|
|
|
|
case VK_LSHIFT:
|
|
|
|
*ksymp = GDK_Shift_L; break;
|
|
|
|
case VK_CONTROL:
|
|
|
|
case VK_LCONTROL:
|
|
|
|
*ksymp = GDK_Control_L; break;
|
|
|
|
case VK_MENU:
|
|
|
|
case VK_LMENU:
|
|
|
|
*ksymp = GDK_Alt_L; break;
|
|
|
|
case VK_PAUSE:
|
|
|
|
*ksymp = GDK_Pause; break;
|
|
|
|
case VK_ESCAPE:
|
|
|
|
*ksymp = GDK_Escape; break;
|
|
|
|
case VK_PRIOR:
|
|
|
|
*ksymp = GDK_Prior; break;
|
|
|
|
case VK_NEXT:
|
|
|
|
*ksymp = GDK_Next; break;
|
|
|
|
case VK_END:
|
|
|
|
*ksymp = GDK_End; break;
|
|
|
|
case VK_HOME:
|
|
|
|
*ksymp = GDK_Home; break;
|
|
|
|
case VK_LEFT:
|
|
|
|
*ksymp = GDK_Left; break;
|
|
|
|
case VK_UP:
|
|
|
|
*ksymp = GDK_Up; break;
|
|
|
|
case VK_RIGHT:
|
|
|
|
*ksymp = GDK_Right; break;
|
|
|
|
case VK_DOWN:
|
|
|
|
*ksymp = GDK_Down; break;
|
|
|
|
case VK_SELECT:
|
|
|
|
*ksymp = GDK_Select; break;
|
|
|
|
case VK_PRINT:
|
|
|
|
*ksymp = GDK_Print; break;
|
|
|
|
case VK_EXECUTE:
|
|
|
|
*ksymp = GDK_Execute; break;
|
|
|
|
case VK_INSERT:
|
|
|
|
*ksymp = GDK_Insert; break;
|
|
|
|
case VK_DELETE:
|
|
|
|
*ksymp = GDK_Delete; break;
|
|
|
|
case VK_HELP:
|
|
|
|
*ksymp = GDK_Help; break;
|
|
|
|
case VK_LWIN:
|
|
|
|
*ksymp = GDK_Meta_L; break;
|
|
|
|
case VK_RWIN:
|
|
|
|
*ksymp = GDK_Meta_R; break;
|
|
|
|
case VK_MULTIPLY:
|
|
|
|
*ksymp = GDK_KP_Multiply; break;
|
|
|
|
case VK_ADD:
|
|
|
|
*ksymp = GDK_KP_Add; break;
|
|
|
|
case VK_SEPARATOR:
|
|
|
|
*ksymp = GDK_KP_Separator; break;
|
|
|
|
case VK_SUBTRACT:
|
|
|
|
*ksymp = GDK_KP_Subtract; break;
|
|
|
|
case VK_DECIMAL:
|
|
|
|
*ksymp = GDK_KP_Decimal; break;
|
|
|
|
case VK_DIVIDE:
|
|
|
|
*ksymp = GDK_KP_Divide; break;
|
|
|
|
case VK_F1:
|
|
|
|
*ksymp = GDK_F1; break;
|
|
|
|
case VK_F2:
|
|
|
|
*ksymp = GDK_F2; break;
|
|
|
|
case VK_F3:
|
|
|
|
*ksymp = GDK_F3; break;
|
|
|
|
case VK_F4:
|
|
|
|
*ksymp = GDK_F4; break;
|
|
|
|
case VK_F5:
|
|
|
|
*ksymp = GDK_F5; break;
|
|
|
|
case VK_F6:
|
|
|
|
*ksymp = GDK_F6; break;
|
|
|
|
case VK_F7:
|
|
|
|
*ksymp = GDK_F7; break;
|
|
|
|
case VK_F8:
|
|
|
|
*ksymp = GDK_F8; break;
|
|
|
|
case VK_F9:
|
|
|
|
*ksymp = GDK_F9; break;
|
|
|
|
case VK_F10:
|
|
|
|
*ksymp = GDK_F10; break;
|
|
|
|
case VK_F11:
|
|
|
|
*ksymp = GDK_F11; break;
|
|
|
|
case VK_F12:
|
|
|
|
*ksymp = GDK_F12; break;
|
|
|
|
case VK_F13:
|
|
|
|
*ksymp = GDK_F13; break;
|
|
|
|
case VK_F14:
|
|
|
|
*ksymp = GDK_F14; break;
|
|
|
|
case VK_F15:
|
|
|
|
*ksymp = GDK_F15; break;
|
|
|
|
case VK_F16:
|
|
|
|
*ksymp = GDK_F16; break;
|
|
|
|
case VK_F17:
|
|
|
|
*ksymp = GDK_F17; break;
|
|
|
|
case VK_F18:
|
|
|
|
*ksymp = GDK_F18; break;
|
|
|
|
case VK_F19:
|
|
|
|
*ksymp = GDK_F19; break;
|
|
|
|
case VK_F20:
|
|
|
|
*ksymp = GDK_F20; break;
|
|
|
|
case VK_F21:
|
|
|
|
*ksymp = GDK_F21; break;
|
|
|
|
case VK_F22:
|
|
|
|
*ksymp = GDK_F22; break;
|
|
|
|
case VK_F23:
|
|
|
|
*ksymp = GDK_F23; break;
|
|
|
|
case VK_F24:
|
|
|
|
*ksymp = GDK_F24; break;
|
|
|
|
case VK_NUMLOCK:
|
|
|
|
*ksymp = GDK_Num_Lock; break;
|
|
|
|
case VK_SCROLL:
|
|
|
|
*ksymp = GDK_Scroll_Lock; break;
|
|
|
|
case VK_RSHIFT:
|
|
|
|
*ksymp = GDK_Shift_R; break;
|
|
|
|
case VK_RCONTROL:
|
|
|
|
*ksymp = GDK_Control_R; break;
|
|
|
|
case VK_RMENU:
|
|
|
|
*ksymp = GDK_Alt_R; break;
|
|
|
|
}
|
|
|
|
if (*ksymp == 0)
|
|
|
|
{
|
|
|
|
if ((k = ToAsciiEx (vk, scancode, key_state,
|
|
|
|
(LPWORD) chars, 0,
|
|
|
|
_gdk_input_locale)) == 1)
|
|
|
|
{
|
|
|
|
if (_gdk_input_codepage == 1252 &&
|
|
|
|
chars[0] >= GDK_space && chars[0] <= GDK_asciitilde)
|
|
|
|
*ksymp = chars[0];
|
|
|
|
else
|
|
|
|
{
|
|
|
|
wchar_t wcs[1];
|
|
|
|
if (MultiByteToWideChar (_gdk_input_codepage, 0,
|
|
|
|
chars, 1, wcs, 1) > 0)
|
|
|
|
*ksymp = gdk_unicode_to_keyval (wcs[0]);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if (*ksymp == 0)
|
|
|
|
*ksymp = GDK_VoidSymbol;
|
|
|
|
}
|
|
|
|
key_state[vk] = 0;
|
|
|
|
}
|
|
|
|
}
|
2002-09-11 21:55:48 +00:00
|
|
|
GDK_NOTE (EVENTS, print_keysym_tab ());
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
}
|
|
|
|
|
2001-06-22 14:08:51 +00:00
|
|
|
GdkKeymap*
|
Changes multihead reorganizing code for win32 support, mostly from a patch
Wed Jun 5 18:34:47 2002 Owen Taylor <otaylor@redhat.com>
Changes multihead reorganizing code for win32 support,
mostly from a patch by Hans Breuer.
* gdk/gdkcolor.c gdk/x11/gdkcolor-x11.c gdk/gdkcursor.c
gdk/x11/gdkcursor-x11.c gdk/gdkevents.c gdk/x11/gdkevents-x11.c
gdk/gdkfont.c gdk/x11/gdkfont-x11.c gdk/gdkkeys.c
gdk/x11/gdkkeys-x11.c gdk/gdkimage.c gdk/x11/gdkimage-x11.c
gdk/gdkscreen.c gdk/x11/gdkmain-x11.c
gdk/gdkdisplay.c gdk/gdkevents-x11.c gdk/gdkpango.c
gdk/x11/gdkpango-x11.c gdk/gdkselection.c
gdk/x11/gdkselection-x11.c gdk/gdkwindow.c
gdk/x11/gdkwindow-x11.c gdk/gdkvisual.c gdk/x11/gdkvisual-x11.c:
Move port-independent singlehead wrapper functions into
port-independent part of GDK. (#80009)
* gdk/win32/gdkcolor-win32.c gdk/win32/gdkcursor-win32.c
gdk/win32/gdkevents-win32.c gdk/win32/gdkfont-win32.c
gdk/win32/gdkimage-win32.c gdk/win32/gdkkeys-win32.c
gdk/win32/gdkmain-win32.c gdk/win32/gdkproperty-win32.c
gdk/win32/gdkselection-win32.c gdk/win32/gkwindow-win32.c:
Turn singlehead functions into "multihead" functions that ignore
their GdkDisplay or GdkScreen arguments.
* gdk/win32/gdkdrawable-win32.c gdk/win32/gdkevents-win32.c
gdk/win32/gdkinput-win32.c gdk/win32/gdkprivate-win32.h:
Misc multihead-compatibility changes.
* gtk/gtk.def gdk/gdk.def: Update for multihead functions.
* gdk/gdkcolormap.h gdk/gdkvisual.h gdk/x11/gdkcolormap-x11.c
gdk/x11/gdkvisual-x11.c: Remove the screen fields
from the public parts of the colormap/visual structures, add accessors
instead.
* gdk/gdkpixbuf-render.c gdk/gdkpixmap.c gdk/gdkrgb.c
gdk/x11/gdkcolormap-x11.c gdk/x11/gdkimage-x11.c
gdk/x11/gdkimage-x11.c gdk/x11/gdkprivate-x11.h gtk/gtkgc.c
gtk/gtkstyle.c gtk/gtkwidget.c: Use accessors to get the screen
for colormaps, visuals; move the fields into the private
structures for the x11 backend.
* gdk/gdkdisplay.[ch] gdk/x11/gdkdisplay-x11.[ch]
gdk/gdkscreen.[ch] gdk/x11/gdkscreen-x11.c:
Remove virtualization of screen and display functions.
(#79990, patch from Erwann Chenede)
* gdk/win32/gdkdisplay-x11.c gdk/win32/gdkscreen-win32.c
gdk/win32/{Makefile.am, makefile.msc, makefile.mingw}:
New files containing stub implementations of Display,
Screen functions.
* gdk/x11/gdkscreen-x11.[ch] gdk/x11/gdkdisplay-x11.[ch]
gdk/x11/gdkx.h: Clean up function exports and what
headers they are in. (#79954)
* gdk/x11/gdkx.h: Fix macro that was referring to a non-existant
screen->screen_num. (In the patch for #79972, Erwann Chenede)
* gdk/gdkscreen.c gdk/gdkwindow.c gdk/x11/gdkinternals.h
gdk/x11/gdkscreen-x11.c: Fix gdk_screen_get_window_at_pointer()
to use window hooks. (#79972, patch partly from Erwann Chenede)
* gdk/x11/gdkdisplay-x11.c gdk/x11/gdkevents-x11.c: Fix
some warnings.
2002-06-06 00:26:42 +00:00
|
|
|
gdk_keymap_get_for_display (GdkDisplay *display)
|
2001-06-22 14:08:51 +00:00
|
|
|
{
|
2002-06-20 23:59:27 +00:00
|
|
|
g_return_val_if_fail (display == gdk_display_get_default (), NULL);
|
Changes multihead reorganizing code for win32 support, mostly from a patch
Wed Jun 5 18:34:47 2002 Owen Taylor <otaylor@redhat.com>
Changes multihead reorganizing code for win32 support,
mostly from a patch by Hans Breuer.
* gdk/gdkcolor.c gdk/x11/gdkcolor-x11.c gdk/gdkcursor.c
gdk/x11/gdkcursor-x11.c gdk/gdkevents.c gdk/x11/gdkevents-x11.c
gdk/gdkfont.c gdk/x11/gdkfont-x11.c gdk/gdkkeys.c
gdk/x11/gdkkeys-x11.c gdk/gdkimage.c gdk/x11/gdkimage-x11.c
gdk/gdkscreen.c gdk/x11/gdkmain-x11.c
gdk/gdkdisplay.c gdk/gdkevents-x11.c gdk/gdkpango.c
gdk/x11/gdkpango-x11.c gdk/gdkselection.c
gdk/x11/gdkselection-x11.c gdk/gdkwindow.c
gdk/x11/gdkwindow-x11.c gdk/gdkvisual.c gdk/x11/gdkvisual-x11.c:
Move port-independent singlehead wrapper functions into
port-independent part of GDK. (#80009)
* gdk/win32/gdkcolor-win32.c gdk/win32/gdkcursor-win32.c
gdk/win32/gdkevents-win32.c gdk/win32/gdkfont-win32.c
gdk/win32/gdkimage-win32.c gdk/win32/gdkkeys-win32.c
gdk/win32/gdkmain-win32.c gdk/win32/gdkproperty-win32.c
gdk/win32/gdkselection-win32.c gdk/win32/gkwindow-win32.c:
Turn singlehead functions into "multihead" functions that ignore
their GdkDisplay or GdkScreen arguments.
* gdk/win32/gdkdrawable-win32.c gdk/win32/gdkevents-win32.c
gdk/win32/gdkinput-win32.c gdk/win32/gdkprivate-win32.h:
Misc multihead-compatibility changes.
* gtk/gtk.def gdk/gdk.def: Update for multihead functions.
* gdk/gdkcolormap.h gdk/gdkvisual.h gdk/x11/gdkcolormap-x11.c
gdk/x11/gdkvisual-x11.c: Remove the screen fields
from the public parts of the colormap/visual structures, add accessors
instead.
* gdk/gdkpixbuf-render.c gdk/gdkpixmap.c gdk/gdkrgb.c
gdk/x11/gdkcolormap-x11.c gdk/x11/gdkimage-x11.c
gdk/x11/gdkimage-x11.c gdk/x11/gdkprivate-x11.h gtk/gtkgc.c
gtk/gtkstyle.c gtk/gtkwidget.c: Use accessors to get the screen
for colormaps, visuals; move the fields into the private
structures for the x11 backend.
* gdk/gdkdisplay.[ch] gdk/x11/gdkdisplay-x11.[ch]
gdk/gdkscreen.[ch] gdk/x11/gdkscreen-x11.c:
Remove virtualization of screen and display functions.
(#79990, patch from Erwann Chenede)
* gdk/win32/gdkdisplay-x11.c gdk/win32/gdkscreen-win32.c
gdk/win32/{Makefile.am, makefile.msc, makefile.mingw}:
New files containing stub implementations of Display,
Screen functions.
* gdk/x11/gdkscreen-x11.[ch] gdk/x11/gdkdisplay-x11.[ch]
gdk/x11/gdkx.h: Clean up function exports and what
headers they are in. (#79954)
* gdk/x11/gdkx.h: Fix macro that was referring to a non-existant
screen->screen_num. (In the patch for #79972, Erwann Chenede)
* gdk/gdkscreen.c gdk/gdkwindow.c gdk/x11/gdkinternals.h
gdk/x11/gdkscreen-x11.c: Fix gdk_screen_get_window_at_pointer()
to use window hooks. (#79972, patch partly from Erwann Chenede)
* gdk/x11/gdkdisplay-x11.c gdk/x11/gdkevents-x11.c: Fix
some warnings.
2002-06-06 00:26:42 +00:00
|
|
|
|
2001-06-22 14:08:51 +00:00
|
|
|
if (default_keymap == NULL)
|
|
|
|
default_keymap = g_object_new (gdk_keymap_get_type (), NULL);
|
|
|
|
|
|
|
|
return default_keymap;
|
|
|
|
}
|
|
|
|
|
|
|
|
PangoDirection
|
|
|
|
gdk_keymap_get_direction (GdkKeymap *keymap)
|
|
|
|
{
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
update_keymap ();
|
2001-06-22 14:08:51 +00:00
|
|
|
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
switch (PRIMARYLANGID (LOWORD ((DWORD) _gdk_input_locale)))
|
|
|
|
{
|
|
|
|
case LANG_HEBREW:
|
|
|
|
case LANG_ARABIC:
|
|
|
|
/* Not 100% sure about these */
|
2002-02-27 16:37:04 +00:00
|
|
|
#ifdef LANG_URDU
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
case LANG_URDU:
|
2002-02-27 16:37:04 +00:00
|
|
|
#endif
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
case LANG_FARSI:
|
|
|
|
/* Others? */
|
|
|
|
return PANGO_DIRECTION_RTL;
|
|
|
|
|
|
|
|
default:
|
|
|
|
return PANGO_DIRECTION_LTR;
|
|
|
|
}
|
2001-06-22 14:08:51 +00:00
|
|
|
}
|
2000-12-14 23:14:18 +00:00
|
|
|
|
|
|
|
gboolean
|
|
|
|
gdk_keymap_get_entries_for_keyval (GdkKeymap *keymap,
|
|
|
|
guint keyval,
|
|
|
|
GdkKeymapKey **keys,
|
|
|
|
gint *n_keys)
|
|
|
|
{
|
|
|
|
GArray *retval;
|
|
|
|
|
|
|
|
g_return_val_if_fail (keymap == NULL || GDK_IS_KEYMAP (keymap), FALSE);
|
|
|
|
g_return_val_if_fail (keys != NULL, FALSE);
|
|
|
|
g_return_val_if_fail (n_keys != NULL, FALSE);
|
|
|
|
g_return_val_if_fail (keyval != 0, FALSE);
|
|
|
|
|
|
|
|
retval = g_array_new (FALSE, FALSE, sizeof (GdkKeymapKey));
|
|
|
|
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
/* Accept only the default keymap */
|
|
|
|
if (keymap == NULL || keymap == gdk_keymap_get_default ())
|
|
|
|
{
|
|
|
|
gint vk;
|
|
|
|
|
|
|
|
update_keymap ();
|
|
|
|
|
|
|
|
for (vk = 0; vk < 256; vk++)
|
|
|
|
{
|
|
|
|
gint i;
|
|
|
|
|
|
|
|
for (i = 0; i < 4; i++)
|
|
|
|
{
|
|
|
|
if (keysym_tab[vk*4+i] == keyval)
|
|
|
|
{
|
|
|
|
GdkKeymapKey key;
|
|
|
|
|
|
|
|
key.keycode = vk;
|
|
|
|
|
|
|
|
/* 2 levels (normal, shift), two groups (normal, AltGr) */
|
|
|
|
key.group = i / 2;
|
|
|
|
key.level = i % 2;
|
|
|
|
|
|
|
|
g_array_append_val (retval, key);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2000-12-14 23:14:18 +00:00
|
|
|
|
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
|
|
|
#ifdef G_ENABLE_DEBUG
|
|
|
|
if (_gdk_debug_flags & GDK_DEBUG_EVENTS)
|
|
|
|
{
|
|
|
|
gint i;
|
|
|
|
|
|
|
|
g_print ("gdk_keymap_get_entries_for_keyval: %#.04x (%s):",
|
|
|
|
keyval, gdk_keyval_name (keyval));
|
|
|
|
for (i = 0; i < retval->len; i++)
|
|
|
|
{
|
|
|
|
GdkKeymapKey *entry = (GdkKeymapKey *) retval->data + i;
|
|
|
|
g_print (" %#.02x %d %d", entry->keycode, entry->group, entry->level);
|
|
|
|
}
|
|
|
|
g_print ("\n");
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
2000-12-14 23:14:18 +00:00
|
|
|
if (retval->len > 0)
|
|
|
|
{
|
|
|
|
*keys = (GdkKeymapKey*) retval->data;
|
|
|
|
*n_keys = retval->len;
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
*keys = NULL;
|
|
|
|
*n_keys = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
g_array_free (retval, retval->len > 0 ? FALSE : TRUE);
|
|
|
|
|
|
|
|
return *n_keys > 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
gboolean
|
|
|
|
gdk_keymap_get_entries_for_keycode (GdkKeymap *keymap,
|
|
|
|
guint hardware_keycode,
|
|
|
|
GdkKeymapKey **keys,
|
|
|
|
guint **keyvals,
|
|
|
|
gint *n_entries)
|
|
|
|
{
|
|
|
|
GArray *key_array;
|
|
|
|
GArray *keyval_array;
|
|
|
|
|
|
|
|
g_return_val_if_fail (keymap == NULL || GDK_IS_KEYMAP (keymap), FALSE);
|
|
|
|
g_return_val_if_fail (n_entries != NULL, FALSE);
|
|
|
|
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
if (hardware_keycode <= 0 ||
|
|
|
|
hardware_keycode >= 256)
|
2000-12-14 23:14:18 +00:00
|
|
|
{
|
|
|
|
if (keys)
|
|
|
|
*keys = NULL;
|
|
|
|
if (keyvals)
|
|
|
|
*keyvals = NULL;
|
|
|
|
|
|
|
|
*n_entries = 0;
|
|
|
|
return FALSE;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (keys)
|
|
|
|
key_array = g_array_new (FALSE, FALSE, sizeof (GdkKeymapKey));
|
|
|
|
else
|
|
|
|
key_array = NULL;
|
|
|
|
|
|
|
|
if (keyvals)
|
|
|
|
keyval_array = g_array_new (FALSE, FALSE, sizeof (guint));
|
|
|
|
else
|
|
|
|
keyval_array = NULL;
|
|
|
|
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
/* Accept only the default keymap */
|
|
|
|
if (keymap == NULL || keymap == gdk_keymap_get_default ())
|
|
|
|
{
|
|
|
|
gint i;
|
|
|
|
|
|
|
|
update_keymap ();
|
|
|
|
|
|
|
|
for (i = 0; i < 4; i++)
|
|
|
|
{
|
|
|
|
if (key_array)
|
|
|
|
{
|
|
|
|
GdkKeymapKey key;
|
|
|
|
|
|
|
|
key.keycode = hardware_keycode;
|
|
|
|
|
|
|
|
key.group = i / 2;
|
|
|
|
key.level = i % 2;
|
|
|
|
|
|
|
|
g_array_append_val (key_array, key);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (keyval_array)
|
|
|
|
g_array_append_val (keyval_array, keysym_tab[hardware_keycode*4+i]);
|
|
|
|
}
|
|
|
|
}
|
2000-12-14 23:14:18 +00:00
|
|
|
|
|
|
|
if ((key_array && key_array->len > 0) ||
|
|
|
|
(keyval_array && keyval_array->len > 0))
|
|
|
|
{
|
|
|
|
if (keys)
|
|
|
|
*keys = (GdkKeymapKey*) key_array->data;
|
|
|
|
|
|
|
|
if (keyvals)
|
|
|
|
*keyvals = (guint*) keyval_array->data;
|
|
|
|
|
|
|
|
if (key_array)
|
|
|
|
*n_entries = key_array->len;
|
|
|
|
else
|
|
|
|
*n_entries = keyval_array->len;
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
if (keys)
|
|
|
|
*keys = NULL;
|
|
|
|
|
|
|
|
if (keyvals)
|
|
|
|
*keyvals = NULL;
|
|
|
|
|
|
|
|
*n_entries = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (key_array)
|
|
|
|
g_array_free (key_array, key_array->len > 0 ? FALSE : TRUE);
|
|
|
|
if (keyval_array)
|
|
|
|
g_array_free (keyval_array, keyval_array->len > 0 ? FALSE : TRUE);
|
|
|
|
|
|
|
|
return *n_entries > 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
guint
|
|
|
|
gdk_keymap_lookup_key (GdkKeymap *keymap,
|
|
|
|
const GdkKeymapKey *key)
|
|
|
|
{
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
guint sym;
|
|
|
|
|
2000-12-14 23:14:18 +00:00
|
|
|
g_return_val_if_fail (keymap == NULL || GDK_IS_KEYMAP (keymap), 0);
|
|
|
|
g_return_val_if_fail (key != NULL, 0);
|
|
|
|
g_return_val_if_fail (key->group < 4, 0);
|
|
|
|
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
/* Accept only the default keymap */
|
|
|
|
if (keymap != NULL && keymap != gdk_keymap_get_default ())
|
|
|
|
return 0;
|
2000-12-14 23:14:18 +00:00
|
|
|
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
update_keymap ();
|
|
|
|
|
|
|
|
if (key->keycode >= 256 ||
|
|
|
|
key->group < 0 || key->group >= 2 ||
|
|
|
|
key->level < 0 || key->level >= 2)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
sym = keysym_tab[key->keycode*4 + key->group*2 + key->level];
|
|
|
|
|
|
|
|
if (sym == GDK_VoidSymbol)
|
|
|
|
return 0;
|
|
|
|
else
|
|
|
|
return sym;
|
2000-12-14 23:14:18 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
gboolean
|
|
|
|
gdk_keymap_translate_keyboard_state (GdkKeymap *keymap,
|
|
|
|
guint hardware_keycode,
|
|
|
|
GdkModifierType state,
|
|
|
|
gint group,
|
|
|
|
guint *keyval,
|
|
|
|
gint *effective_group,
|
|
|
|
gint *level,
|
2002-02-21 17:14:10 +00:00
|
|
|
GdkModifierType *consumed_modifiers)
|
2000-12-14 23:14:18 +00:00
|
|
|
{
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
guint tmp_keyval;
|
2002-03-06 00:36:08 +00:00
|
|
|
guint tmp_modifiers;
|
|
|
|
guint *keyvals;
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
gint shift_level;
|
2002-03-06 00:36:08 +00:00
|
|
|
gboolean ignore_shift = FALSE;
|
|
|
|
gboolean ignore_group = FALSE;
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
|
2000-12-14 23:14:18 +00:00
|
|
|
g_return_val_if_fail (keymap == NULL || GDK_IS_KEYMAP (keymap), FALSE);
|
|
|
|
g_return_val_if_fail (group < 4, FALSE);
|
|
|
|
|
2002-03-06 00:36:08 +00:00
|
|
|
GDK_NOTE (EVENTS, g_print ("gdk_keymap_translate_keyboard_state: keycode=%#x state=%#x group=%d\n",
|
|
|
|
hardware_keycode, state, group));
|
|
|
|
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
if (keyval)
|
|
|
|
*keyval = 0;
|
|
|
|
if (effective_group)
|
|
|
|
*effective_group = 0;
|
|
|
|
if (level)
|
|
|
|
*level = 0;
|
|
|
|
if (consumed_modifiers)
|
|
|
|
*consumed_modifiers = 0;
|
|
|
|
|
|
|
|
/* Accept only the default keymap */
|
|
|
|
if (keymap != NULL && keymap != gdk_keymap_get_default ())
|
|
|
|
return FALSE;
|
|
|
|
|
|
|
|
if (hardware_keycode >= 256)
|
|
|
|
return FALSE;
|
|
|
|
|
|
|
|
if (group < 0 || group >= 2)
|
|
|
|
return FALSE;
|
|
|
|
|
|
|
|
if ((state & GDK_SHIFT_MASK) && (state & GDK_LOCK_MASK))
|
|
|
|
shift_level = 0; /* shift disables shift lock */
|
|
|
|
else if ((state & GDK_SHIFT_MASK) || (state & GDK_LOCK_MASK))
|
|
|
|
shift_level = 1;
|
|
|
|
else
|
|
|
|
shift_level = 0;
|
|
|
|
|
|
|
|
update_keymap ();
|
|
|
|
|
2002-03-06 00:36:08 +00:00
|
|
|
keyvals = keysym_tab + hardware_keycode*4;
|
|
|
|
|
|
|
|
/* Drop group and shift if there are no keysymbols on
|
|
|
|
* the key for those.
|
|
|
|
*/
|
|
|
|
if (shift_level == 1 &&
|
|
|
|
keyvals[group*2 + 1] == GDK_VoidSymbol &&
|
|
|
|
keyvals[group*2] != GDK_VoidSymbol)
|
|
|
|
{
|
|
|
|
shift_level = 0;
|
|
|
|
ignore_shift = TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (group == 1 &&
|
|
|
|
keyvals[2 + shift_level] == GDK_VoidSymbol &&
|
|
|
|
keyvals[0 + shift_level] != GDK_VoidSymbol)
|
|
|
|
{
|
|
|
|
group = 0;
|
|
|
|
ignore_group = TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (keyvals[group *2 + shift_level] == GDK_VoidSymbol &&
|
|
|
|
keyvals[0 + 0] != GDK_VoidSymbol)
|
|
|
|
{
|
|
|
|
shift_level = 0;
|
|
|
|
group = 0;
|
|
|
|
ignore_group = TRUE;
|
|
|
|
ignore_shift = TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* See whether the group and shift level actually mattered
|
|
|
|
* to know what to put in consumed_modifiers
|
|
|
|
*/
|
|
|
|
if (keyvals[group*2 + 1] == GDK_VoidSymbol ||
|
|
|
|
keyvals[group*2 + 0] == keyvals[group*2 + 1])
|
|
|
|
ignore_shift = TRUE;
|
|
|
|
|
|
|
|
if (keyvals[2 + shift_level] == GDK_VoidSymbol ||
|
|
|
|
keyvals[0 + shift_level] == keyvals[2 + shift_level])
|
|
|
|
ignore_group = TRUE;
|
|
|
|
|
|
|
|
tmp_keyval = keyvals[group*2 + shift_level];
|
|
|
|
|
|
|
|
tmp_modifiers = ignore_group ? 0 : GDK_MOD2_MASK;
|
|
|
|
tmp_modifiers |= ignore_shift ? 0 : (GDK_SHIFT_MASK | GDK_LOCK_MASK);
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
|
|
|
|
if (effective_group)
|
|
|
|
*effective_group = group;
|
|
|
|
|
|
|
|
if (level)
|
|
|
|
*level = shift_level;
|
|
|
|
|
|
|
|
if (consumed_modifiers)
|
2002-03-06 00:36:08 +00:00
|
|
|
*consumed_modifiers = tmp_modifiers;
|
Implement the functions that until now just were non-functional stubs. For
2002-02-26 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkkeys-win32.c: Implement the functions that until
now just were non-functional stubs. For "hardware keycodes", we
use Windows virtual keycodes. Not scancodes, although that at
first might seem more low-level and a better match to X11
keycodes.
The Windows API is really mixed up and confused with respect to
scancodes and virtual keycodes. (Surprised?) Some scancodes are
generated by two keys on the keyboard (!), and although the
keyboard messages do have a flag to indicate which key the user
pressed, other API that take a scan code as input don't let you
specify which actual key you mean.
(update_keymap): Function to build a X11-like representation of
the keyboard. Each key has four keysyms: two levels (nonshifted
and shifted) and two groups (normal and with AltGr).
(gdk_keymap_get_direction): Use the codepage corresponding to the
thread's input locale, not the system codepage.
* gdk/win32/gdkglobals-win32.c
* gdk/win32/gdkmain-win32.c
* gdk/win32/gdkprivate-win32.h
* gdk/win32/gdkwindow-win32.h
* gdk/win32/gdkwindow-win32.c: Remove the input_locale and
charset_info fields from GdkWindowImplWin32. Input locale is
per-thread in Windows, and as GDK on Windows really only works
when the GDI interaction all happens in just one thread anyway,
this state can be global. Use globals _gdk_input_locale and
_gdk_input_codepage instead. Set these based on the thread's input
locale (keyboard layout, or which IME is active).
* gdk/win32/gdkevents-win32.c: Set the group and hardware_keycode
fields in GDK key events. On input locale change messages, set
the global state variables, and inform update_keymap() that it
has to rebuild the keymap.
2002-02-26 01:18:27 +00:00
|
|
|
|
|
|
|
if (keyval)
|
|
|
|
*keyval = tmp_keyval;
|
2000-12-14 23:14:18 +00:00
|
|
|
|
2002-03-06 00:36:08 +00:00
|
|
|
GDK_NOTE (EVENTS, g_print ("...group=%d level=%d cmods=%#x keyval=%s\n",
|
|
|
|
group, shift_level, tmp_modifiers, gdk_keyval_name (tmp_keyval)));
|
|
|
|
|
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
|
|
|
return tmp_keyval != GDK_VoidSymbol;
|
2000-12-14 23:14:18 +00:00
|
|
|
}
|