[prev in list] [next in list] [prev in thread] [next in thread] 

List:       enlightenment-devel
Subject:    [E-devel] =?utf-8?q?_ecore=5Fevent=5Fhandler=5Fadd_works_differen?= =?utf-8?q?tly_in_X_and_Wayland?=
From:       김재환 <greensun00 () naver ! com>
Date:       2015-05-21 1:19:02
Message-ID: 2c8c875243db6b5f14639d086e1416a () cweb16 ! nm ! nhnsystem ! com
[Download RAW message or body]

 
ecore_event_handler_add works differently.
 
In X, ecore_event_handler_add and elm_win_add works well. elm_win_add and \
ecore_event_handler_add works well,too. The ecore_event_handler_add works well \
regardless of creating window(or ecore_evas).  
But In Wayland, if we uses ecore_event_handler_add before elm_win_add, it fails.
The reason is ecore_event_init is not called at that time.
In X, ecore_event_init is called by ecore_x_init(this is called _elm_config_sub_init) \
before creating window.   
It means the API operation is different as a display server. 
So we should make them work same.
 
To make ecore_event_handler_add works well before creating window, I added \
ecore_wl_init in _elm_config_sub_init. Then It works well.
Is this change right?
Or is there any other solution?
 
블로그서명greensun00님의 블로그
안녕하세요.
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


[prev in list] [next in list] [prev in thread] [next in thread]