From 45cd12cccfc4c86d14d944502fe412cde93ab77b Mon Sep 17 00:00:00 2001 From: Pietro Gagliardi Date: Wed, 26 Mar 2014 23:12:48 -0400 Subject: [PATCH] Printed the hardware_keycode on GTK+ Area key events... something came up so I think I might be able to do what I originally wanted to do with keyboards... also more TODOs. --- area_unix.go | 1 + todo.md | 1 + 2 files changed, 2 insertions(+) diff --git a/area_unix.go b/area_unix.go index 36a7eb8..2c3a0dc 100644 --- a/area_unix.go +++ b/area_unix.go @@ -179,6 +179,7 @@ func doKeyEvent(event *C.GdkEvent, data C.gpointer, up bool) bool { var ke KeyEvent e := (*C.GdkEventKey)(unsafe.Pointer(event)) +fmt.Println("$$", up, e.hardware_keycode) s := (*sysData)(unsafe.Pointer(data)) keyval := e.keyval if extkey, ok := extkeys[keyval]; ok { diff --git a/todo.md b/todo.md index ad853ae..a77511b 100644 --- a/todo.md +++ b/todo.md @@ -81,6 +81,7 @@ super ultra important things: - resizing seems to be completely and totally broken in the Wayland backend - scrolling Areas in wine by clicking in the page scroll area often causes the main thread to lock up; uitask does not - make sure the first and last rows and columns of an Area are being drawn on Windows +- clicking on Areas in GTK+ don't bring keyboard focus to them? important things: - make specific wording in documentation consistent (make/create, etc.)