summaryrefslogtreecommitdiff
path: root/src/lib/ecore_evas/ecore_evas_ews.c
diff options
context:
space:
mode:
authorJiyoun Park <jijibe99@gmail.com>2013-02-15 09:32:40 +0000
committerJiyoun Park <jijibe99@gmail.com>2013-02-15 09:32:40 +0000
commitc5a8a6b5ff3da760fdd5018fdfba05cc2b82588e (patch)
tree021977392dcc128263818e9c118dfd8ae94e25b4 /src/lib/ecore_evas/ecore_evas_ews.c
parent98854667875ef83fc18a393a5d26b30603984b97 (diff)
Add infrastructure to handle message between ecore and parent ecore in Ecore_Evas
I add new example related with this. (ecore_evas_extn_socket & plug example) ecore extn use this infrasturcture, server app and client app can communicate each other later, this can be used to contorl access message SVN revision: 83942
Diffstat (limited to 'src/lib/ecore_evas/ecore_evas_ews.c')
-rw-r--r--src/lib/ecore_evas/ecore_evas_ews.c4
1 files changed, 3 insertions, 1 deletions
diff --git a/src/lib/ecore_evas/ecore_evas_ews.c b/src/lib/ecore_evas/ecore_evas_ews.c
index 4f52ae2cba..936b70a415 100644
--- a/src/lib/ecore_evas/ecore_evas_ews.c
+++ b/src/lib/ecore_evas/ecore_evas_ews.c
@@ -697,7 +697,9 @@ static const Ecore_Evas_Engine_Func _ecore_ews_engine_func =
697 697
698 _ecore_evas_ews_render, 698 _ecore_evas_ews_render,
699 _ecore_evas_ews_screen_geometry_get, 699 _ecore_evas_ews_screen_geometry_get,
700 NULL // screen_dpi_get 700 NULL, // screen_dpi_get
701 NULL,
702 NULL // msg_send
701}; 703};
702 704
703void 705void