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.
This commit is contained in:
parent
f5084c07d4
commit
45cd12cccf
|
@ -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 {
|
||||
|
|
1
todo.md
1
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.)
|
||||
|
|
Loading…
Reference in New Issue