summaryrefslogtreecommitdiff
path: root/src/lib/elementary/efl_access_object.c
Commit message (Collapse)AuthorAgeFilesLines
* build: fix elm header usageMike Blumenkrantz2019-09-181-2/+0
| | | | | | | | | | | | .c files in src/lib/elementary should only include elm_priv.h to ensure that all the include ordering is correct and that all necessary headers are pulled in .c files outside of src/lib/elementary should include either/both Efl_Ui.h, Elementary.h as needed Reviewed-by: Stefan Schmidt <stefan@datenfreihafen.org> Differential Revision: https://phab.enlightenment.org/D9978
* efl_access: if 0 is set as reading_info_type, remove existing reading_infoShilpa Singh2019-03-251-0/+7
| | | | | | | | | | | | | | | | | | | | | | | Summary: if 0 is set as reading_info_type, remove existing reading_info and allow default reading info types (name, role, state and description) to be read. Do not set reading info again in reading_info_type_set API if new value matches the old value. Test Plan: If application does not set reading_info_type or set 0 reading_info_type, All four reading info types of an accessible object should be read on highlight. Signed-off-by: Shilpa Singh <shilpa.singh@samsung.com> Reviewers: kimcinoo, jsuya, bu5hm4n, lukasz.stanislawski Subscribers: prasoonsingh16, rajeev.jnnce, #reviewers, cedric, #committers Tags: #efl Differential Revision: https://phab.enlightenment.org/D8435
* efl_access: Add attribute_del API, Add test cases for all ↵Shilpa Singh2019-03-201-1/+24
| | | | | | | | | | | | access_object_attribute* APIs Add attribute_del API, currently there is no provision to delete a particular attribute(key-value pair) from the attribute list of a widget. Add test cases for efl_access_attribute_append, efl_access_attributes_get, efl_access_attribute_del and efl_access_attributes_clear API Reviewed-by: Marcel Hollerbach <mail@marcel-hollerbach.de> Reviewed-by: Shinwoo Kim <cinoo.kim@samsung.com> Differential Revision: https://phab.enlightenment.org/D8386
* eolian: drop class function overridingMarcel Hollerbach2019-02-131-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Until this commit eo did class functions as part of the vtable, which enabled those functions to be overwritten in classes inheriting another class. However in task T7675 we decided that this is not really good for bindings, as most OOP languages do not support this sort of feature. After this commit eolian realizes class function completly outside of the vtable, the c-symbol that is the class funciton is now just directly redirecting to a implementation, without the involvement of the vtable. This also means a change to the syntax created by eo: Calling before: class_function(CLASS_A); Calling after: class_function(); Implementation before: class_function(const Eo *obj, void *pd) { ... } Implementation after: class_function(void) { ... } This fixes T7675. Co-authored-by: lauromauro <lauromoura@expertisesolutions.com.br> Reviewed-by: Daniel Kolesa <daniel@octaforge.org> Differential Revision: https://phab.enlightenment.org/D7901
* elm: prevent from accessing null pointer after memory allocationWooHyun Jung2019-01-291-0/+1
| | | | | | | | | | | | | | | | Summary: Add null checking code just after allocating memory Test Plan: make check Reviewers: jypark, Jaehyun_Cho, zmike Reviewed By: Jaehyun_Cho, zmike Subscribers: devilhorns, zmike, cedric, #reviewers, #committers Tags: #efl Differential Revision: https://phab.enlightenment.org/D7801
* efl_access: add free functions to efl_acces_object typesMarcel Hollerbach2019-01-221-4/+10
| | | | | | | | there are owned types in eolian, therefore a free function should be defined on the types that are owned. Reviewed-by: Lukasz Stanislawski <l.stanislaws@samsung.com> Differential Revision: https://phab.enlightenment.org/D7711
* elementary: small correction in the API of Efl.Access.Object to have proper ↵Cedric BAIL2018-05-241-117/+68
| | | | | | | | | | lifecycle. This API require more review, I have just fixed API that return type that are inconsistent over time and fail to allow for proper lifecycle of event, which lead to crash when those event trigger at unexpected point. Differential Revision: https://phab.enlightenment.org/D6102
* Efl.Access.Object (from Efl.Access)Xavi Artigas2018-04-241-0/+707
Ref https://phab.enlightenment.org/T6847 Reviewed-by: Cedric Bail <cedric@osg.samsung.com>