Languages

Menu
Sites
Language
Alternative to Undocumented APIs for cocos2d

I have the problem with undocumented API when using cocos2d v3.5-tizen.

How to alternate the API below?

evas_init
elm_entry_drop_disabled_set
ecore_imf_context_event_callback_add
app_main
elm_entry_drag_disabled_set
evas_shutdown
ecore_imf_context_input_panel_event_callback_add

 

Thanks for your advise!

Tung

 

List

Responses

4 Replies
daniel kim

Hi

I would suggest you to post same query to forum of cocos2d like as following.

   http://discuss.cocos2d-x.org/#

Regards.

pius lee

evas_init, evas_shutdown :

  - There are no alternative to these API. but, If you calll ui_app_main, evas_init will be called internally.

elm_entry_drop_disabled_set, elm_entry_drag_disabled_set :

  - These API was oped only on old test platform (Redwood) why use these? no alternative.

app_main :

  - It can be replace with ui_app_main

ecore_imf_context_event_callback_add, ecore_imf_context_input_panel_event_callback_add : 

  - ecore_imf module is not opened on tizen 2.3. I think you can't make custom text input component.

 

 

Sukwon Suh

I'm sorry about late reply.

 

I'm trying to submit bug fix to main branch of cocos2d-x.

Before that, please visit my local repository below.

https://github.com/sukwonsuh/cocos2d-x

 

This branch fixed undocumented API problem.

Please git clone or download ZIP file in bugfix_cocos2d-x-3.5-tizen branch.

 

Thank you.

Sukwon Suh.

 

Carsten Haitzler

this frankly is a bug with our api checking. it needs to be fixed. there is work underway to do this and "relax" these api checks. specifically evas_init/shutdown, ecore_imf_* calls and elm_entry_* calls.