summaryrefslogtreecommitdiff
path: root/src/modules/ecore_evas/engines/win32
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/modules/ecore_evas/engines/win32
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/modules/ecore_evas/engines/win32')
-rw-r--r--src/modules/ecore_evas/engines/win32/ecore_evas_win32.c4
1 files changed, 3 insertions, 1 deletions
diff --git a/src/modules/ecore_evas/engines/win32/ecore_evas_win32.c b/src/modules/ecore_evas/engines/win32/ecore_evas_win32.c
index b6a9fc563c..73012e4f66 100644
--- a/src/modules/ecore_evas/engines/win32/ecore_evas_win32.c
+++ b/src/modules/ecore_evas/engines/win32/ecore_evas_win32.c
@@ -1152,7 +1152,9 @@ static Ecore_Evas_Engine_Func _ecore_win32_engine_func =
1152 1152
1153 NULL, // render 1153 NULL, // render
1154 NULL, // screen_geometry_get 1154 NULL, // screen_geometry_get
1155 _ecore_evas_win32_screen_dpi_get 1155 _ecore_evas_win32_screen_dpi_get,
1156 NULL,
1157 NULL // msg_send
1156}; 1158};
1157 1159
1158#endif /* BUILD_ECORE_EVAS_WIN32 */ 1160#endif /* BUILD_ECORE_EVAS_WIN32 */