On Sun, 23 Nov 2014 16:23:19 +0100 Tomasz Olszak <[email protected]> said:
> Hello,
>
> I was reviewing Tizen 2.3 native API and ran into this example[1]:
>
> int main(int argc, char* argv[])
> {
> appdata_s ad = {0,};
> service_app_lifecycle_callback_s event_callback = {0,};
>
> dlog_print(DLOG_DEBUG, LOG_TAG, "%s", __func__);
>
> event_callback.create = service_app_create;
> event_callback.terminate = service_app_terminate;
> event_callback.app_control = service_app_control;
>
> dlog_print(DLOG_DEBUG, LOG_TAG, "service_app_main() is called.");
> return service_app_main(argc, argv, &event_callback, &ad);
> }
>
> I looked into service_app_main docs[2] and saw that:
> service_app_main - Runs the main loop of the application until
> service_app_exit() is called.
>
> Question: How to use native API with applications/services which have
> their own event loop?
>
> [1]
> https://developer.tizen.org/dev-guide/2.3.0/org.tizen.mobile.native.appprogramming/html/tutorials/app_tutorial/service_app_tutorial.htm
> [2]
> https://developer.tizen.org/dev-guide/2.3.0/org.tizen.mobile.native.apireference/group__CAPI__SERVICE__APP__MODULE.html#gaad16526cf28a7365b795659e49ee368a
you make the app use the core event loop. (i.e. remove the app event loop and
replace it).
--
Carsten Haitzler (The Rasterman) <[email protected]>
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev