diff options
author | Emmanuele Bassi <ebassi@linux.intel.com> | 2010-04-28 16:19:37 +0100 |
---|---|---|
committer | Emmanuele Bassi <ebassi@linux.intel.com> | 2010-04-28 16:19:37 +0100 |
commit | ce261025f6dfd34153382cb69bcb7fb11b8e2561 (patch) | |
tree | 30688e92d55ed4c3802eedc3c7de516973e257f6 /clutter/clutter-event.c | |
parent | b7098563c26bb6e0f1992bb7c4cb711fbe0424ac (diff) | |
download | clutter-ce261025f6dfd34153382cb69bcb7fb11b8e2561.tar.gz |
Fix clutter_event_get_coords() for crossing events
The ClutterCrossingEvent data structure contains the coordinates
of the crossing; they are regularly filed out by Clutter and by
the backend event processing code. And yet clutter_event_get_coords()
returns (0, 0) because it thinks that CLUTTER_ENTER and CLUTTER_LEAVE
events do not have coordinates.
Diffstat (limited to 'clutter/clutter-event.c')
-rw-r--r-- | clutter/clutter-event.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/clutter/clutter-event.c b/clutter/clutter-event.c index 6e91be8f0..4eec2205d 100644 --- a/clutter/clutter-event.c +++ b/clutter/clutter-event.c @@ -145,8 +145,12 @@ clutter_event_get_coords (ClutterEvent *event, case CLUTTER_DESTROY_NOTIFY: case CLUTTER_CLIENT_MESSAGE: case CLUTTER_DELETE: + break; + case CLUTTER_ENTER: case CLUTTER_LEAVE: + event_x = event->crossing.x; + event_y = event->crossing.y; break; case CLUTTER_BUTTON_PRESS: |