Ok, This actually fixes maximized state properly now :) Basically, we

still need to account for frame height, but not frame width when we
are maximizing.

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

diff --git a/src/modules/ecore_evas/engines/wayland/ecore_evas_wayland_common.c b/src/modules/ecore_evas/engines/wayland/ecore_evas_wayland_common.c
index 7d3d444..4b99563 100644 (file)
--- a/src/modules/ecore_evas/engines/wayland/ecore_evas_wayland_common.c
+++ b/src/modules/ecore_evas/engines/wayland/ecore_evas_wayland_common.c
@@ -224,19 +224,20 @@ _ecore_evas_wl_common_cb_window_configure(void *data EINA_UNUSED, int type EINA_
 
    nw = ev->w;
    nh = ev->h;
-   if ((!ee->prop.maximized) && (!ee->prop.fullscreen))
+
+   if (!ee->prop.fullscreen)
      {
         int fw = 0, fh = 0;
 
         evas_output_framespace_get(ee->evas, NULL, NULL, &fw, &fh);
         if ((ee->rotation == 90) || (ee->rotation == 270))
           {
-             nw = ev->w - fh;
+             if (!ee->prop.maximized) nw = ev->w - fh;
              nh = ev->h - fw;
           }
         else
           {
-             nw = ev->w - fw;
+             if (!ee->prop.maximized) nw = ev->w - fw;
              nh = ev->h - fh;
           }
      }