elementary: Fix calling ecore_evas_wayland_move with improper values

Summary: As ecore_evas_wayland_move ends up updating the location of
the ecore_wl_window, we should be calling move with the proper
geometry as this ends up updating the internal ecore_wl_window
geometry (which in turn sends to xdg_surface_set_window_geometry).
This is part of a fix where xdg_surface_set_window_geometry was
getting sent inproper values.

@fix

Signed-off-by: Chris Michael <cp.michael@samsung.com>

diff --git a/src/lib/elm_win.c b/src/lib/elm_win.c
index 65388e3..6250cf9 100644 (file)
--- a/src/lib/elm_win.c
+++ b/src/lib/elm_win.c
@@ -2619,6 +2619,8 @@ _elm_win_frame_cb_move_start(void *data,
                              const char *sig EINA_UNUSED,
                              const char *source)
 {
+   int ox, oy;
+
    ELM_WIN_DATA_GET(data, sd);
 
    if (!sd) return;
@@ -2638,7 +2640,9 @@ _elm_win_frame_cb_move_start(void *data,
     * position. The new position will get updated automatically when
     * the move is finished */
 
-   ecore_evas_wayland_move(sd->ee, sd->screen.x, sd->screen.y);
+   edje_object_part_geometry_get(sd->frame_obj, "elm.spacer.opaque",
+                                 &ox, &oy, NULL, NULL);
+   ecore_evas_wayland_move(sd->ee, ox, oy);
 }
 
 static void