mirror of
https://github.com/brl/mutter.git
synced 2024-12-25 12:32:05 +00:00
clutter/text: Make update_cursor_location() operate in stage coordinates
Until now we would `clutter_input_focus_set_cursor_location` with cursor-rectangle-in-physical-pixels + actor-location-in-stage-coordinates. But those use different scaling factors so it only got the right answer when the framebuffer scale was 1.0. This directly determines the geometry of the invisible dummy cursor in gnome-shell ibusCandidatePopup.js: ``` panelService.connect('set-cursor-location', (ps, x, y, w, h) => { this._setDummyCursorGeometry(x, y, w, h); }); ``` And because it's invisible it wasn't obvious that it was wrong until you enable `CLUTTER_PAINT=damage-region` and you can see its ghost at the wrong offset and scale. So now we `clutter_input_focus_set_cursor_location` using purely unscaled stage coordinates. And `CLUTTER_PAINT=damage-region` shows that gnome-shell's `_dummyCursor` is placed precisely over the visible cursor. Fixes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3399 and probably other IBus issues that arise when using framebuffer scaling. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1576>
This commit is contained in:
parent
db30a4d7b4
commit
ebf9f18080
@ -1307,7 +1307,7 @@ update_cursor_location (ClutterText *self)
|
||||
if (!priv->editable)
|
||||
return;
|
||||
|
||||
rect = priv->cursor_rect;
|
||||
clutter_text_get_cursor_rect (self, &rect);
|
||||
clutter_actor_get_transformed_position (CLUTTER_ACTOR (self), &x, &y);
|
||||
graphene_rect_offset (&rect, x, y);
|
||||
clutter_input_focus_set_cursor_location (priv->input_focus, &rect);
|
||||
|
Loading…
Reference in New Issue
Block a user