On Thu, Nov 29, 2012 at 11:41 AM, Christopher Michael
cp.mich...@samsung.com wrote:
On 29/11/12 13:27, Eduardo Lima (Etrunko) wrote:
On Thu, Nov 29, 2012 at 5:46 AM, Christopher Michael
cp.mich...@samsung.com wrote:
On 29/11/12 03:11, zhiwen...@linux.intel.com wrote:
From: Alex
On Thu, Nov 29, 2012 at 5:46 AM, Christopher Michael
cp.mich...@samsung.com wrote:
On 29/11/12 03:11, zhiwen...@linux.intel.com wrote:
From: Alex Wuzhiwen...@linux.intel.com
Every touch down event should be converted into mouse in +
mouse button. So we should let every mouse in event go in
On 29/11/12 13:27, Eduardo Lima (Etrunko) wrote:
On Thu, Nov 29, 2012 at 5:46 AM, Christopher Michael
cp.mich...@samsung.com wrote:
On 29/11/12 03:11, zhiwen...@linux.intel.com wrote:
From: Alex Wuzhiwen...@linux.intel.com
Every touch down event should be converted into mouse in +
mouse
From: Alex Wu zhiwen...@linux.intel.com
Every touch down event should be converted into mouse in +
mouse button. So we should let every mouse in event go in the
_ecore_evas_wl_common_cb_mouse_in(), instead of preventing it by
if (!ee-in). Besides that, the coordinates carried by mouse in
event
On 29/11/12 03:11, zhiwen...@linux.intel.com wrote:
From: Alex Wuzhiwen...@linux.intel.com
Every touch down event should be converted into mouse in +
mouse button. So we should let every mouse in event go in the
_ecore_evas_wl_common_cb_mouse_in(), instead of preventing it by
if (!ee-in).
