diff options
| author | Pietro Gagliardi <[email protected]> | 2014-05-10 14:27:29 -0400 |
|---|---|---|
| committer | Pietro Gagliardi <[email protected]> | 2014-05-10 14:27:29 -0400 |
| commit | fefab429fceff15171b47e6583b088ce19716fcd (patch) | |
| tree | 7fde3a113b76c7b4c69d63479fb90a7d3112105f /todo.md | |
| parent | 605ea3123b8efc567b562c276f235dd119dc6de4 (diff) | |
Documented dragging issues caused by how Mac OS X handles mouse events; also determined that multiple buttons held at once only generates one mouseDragged: signal.
Diffstat (limited to 'todo.md')
| -rw-r--r-- | todo.md | 3 |
1 files changed, 0 insertions, 3 deletions
@@ -16,10 +16,7 @@ super ultra important things: - OS X: handle Insert/Help key change in a sane and deterministic way - will need old and new Mac keyboards... - make sure MouseEvent's documentation has dragging described correctly (both Windows and GTK+ do) - - figure out what to do about dragging into or out of a window; will likely need to be undefined as well... - pin down whether or not a click event gets sent if this click changes from a different window to the one with the Area -- determine if, on Mac OS X, dragging with two mouse buttons triggers both xxxMouseDragged: events -- figure out what happens if the mouse button is held on another application, then dragged over an Area without activating that window - double-check to make sure MouseEvent.Held[] is sorted on all platforms - cap click count to 2 on all platforms - the windows build appears to be unstable: |