Re: [E-devel] Windows API & Theme changes

2016-11-24 Thread Jean-Philippe André
Hi, I have pushed a "fix" but I don't like it. All it does is disable shadows and fix the opaque/input region of the window as exposed to Wayland, and fix a 1 pixel offset in the theme. I don't like it because --IMHO-- E should not have SSD (server-side decorations) in Wayland. Also I don't like

Re: [E-devel] Windows API & Theme changes

2016-11-23 Thread Jean-Philippe André
Hey, On 24 November 2016 at 00:09, Mike Blumenkrantz < michael.blumenkra...@gmail.com> wrote: > Hi, > > Mouse eventing works under Wayland compositors by > calling wl_pointer_send_button() on a surface resource. The client then > receives this event and handles it appropriately, in our case by >

Re: [E-devel] Windows API & Theme changes

2016-11-23 Thread Mike Blumenkrantz
Hi, Mouse eventing works under Wayland compositors by calling wl_pointer_send_button() on a surface resource. The client then receives this event and handles it appropriately, in our case by propagating it ecore-wl2 -> ecore-input-evas -> evas. I would hope that in future cases of significant pat

Re: [E-devel] Windows API & Theme changes

2016-11-23 Thread Jean-Philippe André
Hi, As of now, I know that these patches have broken the following things: 1. E internal windows in E Wayland. The borders had disappeared ("fixed") but mouse inputs still don't work. 2. Window border shows EFL CSD + system decorations on Ubuntu (?) For 1. I need help from E/WL experts. I can see

[E-devel] Windows API & Theme changes

2016-11-22 Thread Jean-Philippe André
Hello everyone, First of all, sorry to send this mail after pushing my changes, rather than before. But I prefer spotting issues and fixing them rather than having to worry about everything during the design & implementation phase. I have been working on a new interface for the Window API, and