ecore_animator_del, and ecore_job_del.
As all efl public free apis get null as valid parameter, we do not need
to check null. I also removed some null check for other free apis which
were right next to timer/animator/job del. After this job code got
cleaner.
There are elm_widget_theme/theme_set/theme_get functions.
In Eolian these functions will be described as "theme" method and
"theme" property. There is clash here.
So add suffix "_apply" to Eo API for "elm_widget_theme".
Summary:
Fixed the warning message.
elm_clock.c: In function 'elm_clock_pause_set':
elm_clock.c:1082:49: warning: declaration of 'pause' shadows a global declaration [-Wshadow]
elm_clock.c: In function '_pause_set':
elm_clock.c:1091:14: warning: declaration of 'pause' shadows a global declaration [-Wshadow]
Reviewers: seoz
CC: nirajkr
Differential Revision: https://phab.enlightenment.org/D403
Being annoyed by different types of eina critical macros - CRI, CRIT,
CRITICAL -, I concluded to unify them to one. Discussed on IRC and
finally, CRI was chosen to meet the consistency with other macros -
ERR, WRN, INF, DBG - in terms of the number of characters.
If there is any missing bits, please let me know.
Summary: This patch add two functions for elm_clock widget - elm_clock_pause_set and elm_clock_pause_get. I've prepared it because I want to do a stopwatch using this widget, but now it is impossible to pause the clock without set an editable mode.
Reviewers: seoz, cedric, stanluk, z.kosinski
Reviewed By: seoz
Differential Revision: https://phab.enlightenment.org/D374
I splited ELM_SAFE_FREE refactoring patches. One commit per each file as recommended.
For the detail, please refer 3072dab12f12fe83fb5a628d15efd5cded11787f.
There are pros and cons but this
1. reduces human mistakes.
2. enhances readability.
3. enhances code quality.
4. removes future bug.
5. was adopted from enlightenment.
This is not all. I will work on enhancing elementary more and more.
1. Do not need to print the same error message from all the widget codes.
2. Even though elm_widget_sub_object_add() can be used internally, there should be no error message at all.
Elm devs should fix it beforehand.
So it looks ok to print the error message in elm_widget_sub_object_add() to force elm devs to fix it.
3. Got additional code cleanups.
Smart data is already initialized so we do not need to re-initialize them if the value equals to 0, NULL, or EINA_FALSE.
Sometimes re-initializing smart data explicitly is needed for readability. So there are left overs.
SVN revision: 82228
+ elm_access_object_register();
+ elm_access_object_unregister();
+ elm_access_text_set();
+ elm_access_text_get();
+ elm_access_cb_set();
These APIs are to use edje part, evas object as an accessible object.
and do not create access object, because access object would be created at run time.
This is different with internal API _elm_access_object_register();
SVN revision: 81659
1. add smart_activate(); to access object.
2. add an API _elm_access_activate_callback_set();
- this callback is called when user wants to activate access object
which would represent widget item or edje part object.
3. add owner referece to the Elm_Access_Info for access object.
4. clock: use _elm_access_activate_callback_set();
SVN revision: 79199
Daniel Juyung Seo
Daniel Zaoui
Jaehwan Kim
WooHyun Jung
ChunEon Park
Yakov Goldberg
Daniel Juyung Seo
Amitesh Singh
Michal Jagiello
Tom Hacohen
Carsten Haitzler
Cedric Bail
Shinwoo Kim
Ryuan Choi
Daniel Juyung Seo
Gustavo Lima Chaves
Shinwoo Kim