Understanding Framework Call Functions for UI Input and Update in Tizen 2.4

Original Created May 24, 2016 | Regeneration Apr 22, 2026

Question

I'm a student currently studying the Tizen 2.4 Core Framework and have two specific questions:

What is the first framework call function when UI input appears (such as clicking a button or text input)?
What framework call function is used when UI updates occur (as an effect of UI input)?

I would appreciate any guidance on these topics.

Answer

Problem Understanding

The user wants to understand the framework's callback mechanism for handling UI input events and subsequent updates in Tizen 2.4 applications.

Solution Methods

For UI input events (button click, text input):
- The primary callback function is event_callback() which handles various input events
- For button clicks specifically, you would typically use button_clicked_cb()
- For text input, the entry_activated_cb() is commonly used
For UI updates following input:
- The framework typically calls ui_update_callback() after processing input events
- You can also manually trigger updates using elm_object_signal_emit() for Elementary UI components

Code Examples

// Example for button click callback
static void
button_clicked_cb(void *data, Evas_Object *obj, void *event_info)
{
    // Handle button click event here
    update_ui(); // Trigger UI update
}

// Example for UI update function
static void
update_ui(void)
{
    // Update UI elements here
    elm_object_text_set(label, "Button was clicked");
}

Additional Tips

Always check the return values of callback functions
Remember to register your callback functions properly using functions like evas_object_event_callback_add()
For more detailed information, refer to the Tizen Native API documentation