Finally finished getting ready for Area keyboard input; now just need to figure out which keys to support. Also a Wayland-related TODO.
This commit is contained in:
parent
18271980cb
commit
e73992ab71
|
@ -775,3 +775,6 @@ If I ever intend on providing alternate text-based widgets, I will need to use `
|
|||
Also this answers the what if a key has been held down and switches away from the program question: Windows does not send a key up.
|
||||
|
||||
This just leaves the GTK+ geometry mapping: there is a way to do it if X11 is the only supported backend, but Wayland exists...
|
||||
[12:29] <ebassi> yes, you can assume that they are the same
|
||||
(irc.gimp.net/#gtk+) ok; that works too I guess
|
||||
let's go!
|
||||
|
|
1
todo.md
1
todo.md
|
@ -76,6 +76,7 @@ super ultra important things:
|
|||
- when resizing a GTK+ window smaller than a certain size, the controls inside will start clipping in bizarre ways (progress bars/entry lines will just cut off; editable comboboxes will stretch slightly longer than noneditable ones; the horizontal scrollbar in Area will disappear smoothly; etc.)
|
||||
- the window background of a GTK+ window seems to be... off - I think it has to do with the GtkLayout
|
||||
- see update 18 March 2014 in README
|
||||
- resizing seems to be completely and totally broken in the Wayland backend
|
||||
|
||||
important things:
|
||||
- make specific wording in documentation consistent (make/create, etc.)
|
||||
|
|
Loading…
Reference in New Issue