summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPietro Gagliardi <[email protected]>2014-05-22 03:44:25 -0400
committerPietro Gagliardi <[email protected]>2014-05-22 03:44:25 -0400
commit6a07a06cb8af67e95b8f796f37f1e69531de87f7 (patch)
treec5bb3537ac3c548961c42f7549d337a3453759c5
parente2ab537474f2f6a7216c810238bc031a8550ace0 (diff)
Updated TODO on modifier keys handling in KeyEvent.
-rw-r--r--todo.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/todo.md b/todo.md
index b3d2f6d..612c74c 100644
--- a/todo.md
+++ b/todo.md
@@ -8,7 +8,12 @@ super ultra important things:
- 10.6 also spits a bunch of NSNoAutoreleasePool() debug log messages even though I thoguht I had everything in an NSAutoreleasePool...
- formalize what happens if Modifiers by themselves are held
- OS X: find out if multiple DIFFERENT modifiers released at once produces multiple events
+ - yes it does
- in general, figure out what to do on multiple events, period
+ - current behavior:
+ - Windows: no modifier release unless one modifier is released while another is still held; I think this can be overcome
+ - Unix: all modifiers send press AND release events; left+right sends two events; release mask == pressed keys | released button
+ - Mac OS X: all modifiers send press AND release events; left+right sends TODO; release mask == pressed keys &^ released button
- OS X: the behavior of Modifiers and other keys is broken: keyDown:/keyUp: events stop being sent when the state of Modifiers changes, which is NOT what we want
- [13:44] <Psy> pietro10: nope, the system decides