diff options
author | Jonas Dreßler <verdre@v0yd.nl> | 2022-12-05 21:01:45 +0100 |
---|---|---|
committer | Marge Bot <marge-bot@gnome.org> | 2023-02-03 12:10:22 +0000 |
commit | a62ae73478d8794b1e96726f194fa30d68d45a99 (patch) | |
tree | 36f99f4d2c49e2c44a1f1806608c2e7350b95270 /clutter/clutter | |
parent | 0f0466fa8e8e0acd85138b9dbd1af3d177547a21 (diff) | |
download | mutter-a62ae73478d8794b1e96726f194fa30d68d45a99.tar.gz |
clutter: Propagate PROXIMITY events up and down the tree
There's no real reason to keep those events exclusive to the stage, some
actors or actions might want to get notified about proximity events too,
so propagate them like any other event.
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2342>
Diffstat (limited to 'clutter/clutter')
-rw-r--r-- | clutter/clutter/clutter-stage.c | 9 |
1 files changed, 2 insertions, 7 deletions
diff --git a/clutter/clutter/clutter-stage.c b/clutter/clutter/clutter-stage.c index 0b2ada5b6..33e744df6 100644 --- a/clutter/clutter/clutter-stage.c +++ b/clutter/clutter/clutter-stage.c @@ -4077,6 +4077,8 @@ clutter_stage_emit_event (ClutterStage *self, case CLUTTER_TOUCH_BEGIN: case CLUTTER_TOUCH_CANCEL: case CLUTTER_TOUCH_END: + case CLUTTER_PROXIMITY_IN: + case CLUTTER_PROXIMITY_OUT: { float x, y; @@ -4089,13 +4091,6 @@ clutter_stage_emit_event (ClutterStage *self, target_actor = entry->current_actor; break; } - - case CLUTTER_PROXIMITY_IN: - case CLUTTER_PROXIMITY_OUT: - { - target_actor = CLUTTER_ACTOR (self); - break; - } } g_assert (target_actor != NULL); |