diff options
| author | Pietro Gagliardi <[email protected]> | 2014-03-20 12:11:56 -0400 |
|---|---|---|
| committer | Pietro Gagliardi <[email protected]> | 2014-03-20 12:11:56 -0400 |
| commit | e517115556a97a1e8b0ce91229ef9ecc955aec71 (patch) | |
| tree | 062c44cb8f638337f37303abf8b37edf7a6f5d00 | |
| parent | 9ea4b1280ac7f18c607c41a36d2f56cc8f56763c (diff) | |
Some fixups in the previous commit.
| -rw-r--r-- | areaplan.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/areaplan.md b/areaplan.md index f27e110..15ce605 100644 --- a/areaplan.md +++ b/areaplan.md @@ -666,8 +666,10 @@ So this leaves character-based input as the only real option. The only two quest --------------------- +<a name="sigh"></a> Actually the real question is: is it possible to just get ONE domain of keyboard input on all platforms? GDK has constants for every possible language... so someone not using a Latin-based keyboard will wind up having their keystorkes rejected by the `GdkDrawingArea`... >Keyboard input **MUST** be well defined, and it must be well defined **NOW**. As the author of the GUI library, I **MUST** guarantee that someone typing a character on the same physical machine on different operating systems each with the same keyboard layout gets the exact same response (with no unwanted side effects), and by extension that the programmer sees the same thing. But things are just different enough to screw this up. + Approach | Windows | GTK+ | Mac OS X ----- | ----- | ----- | ----- Virtual key code mapping | Adjusted by layout | Adjusted by layout | NOT adjusted by layout |