Code clean up.

Code clean up.

Fixed can't get textblock's text when edje has no size.

Oops i didn't check upstream efl-test-suite.
I checked efl-test-suite on tizen. it passed all test cases so i made a commit.

The result of "ELM_FIRST_FRAME=T elementary_test " is below.

There may be multiple exception cases, and this patch may look incorrect because of logic I'm not familiar with.

I will list up APIs without TC and init them till 11/11

@zmike @q66 ping?

@devilhorns That sounds reasonable. thanks.

@zmike It seems that a lot of @beta classes use void_ptr though, can't we change all of them after beta?
Anyways, @q66 could you give me advice about it?

• Delete useless log

Code clean up.

Those APIs created for two or more input areas.

It seems to be a commit to help calculate the size.
Among widgets that inherit layout, we need to consider more cases of increasing and decreasing size.

fix code indentations

D10000 I made a commit for my parts (Efl.Threadio, Efl.Appthread)

@woohyun I agree with that. the clock class should support only clock feature(time tick, time showing include sec etc...)

Okay then i agree with ur opinion.

Good

@bu5hm4n Thank you for the detail.

@bu5hm4n Could you please tell me more detail about above comment? mouse-wheel thing i mean.

First Design Concept.

@segfaultxavi Sorry i'm late.

Yes, i do. I think there is nothing wrong with it.

I didn't know that there was a confusion in usability.
When we designing format interface between two or three people who knew the usability of both properties.

@Jaehyun_Cho ping?

For this Input prefix looks more meaningful.
But When i add Input prefix for gesture manager.
It looks implementing efl_input_types and events, Actually not though.
I think it is confusing to use.

Thanks for giving your opinion here.

Thanks. i check the C# build pass through the second way meson build as well.

Fix C# build error.

mesong build support

Meson build support

ignore this warnings

Code clean up to following comments.

I don't see kind of the "gcc=-Wno-clobbered" build options in efl, Do we need to declare variables like this to avoid build warning?

more configs

4. Supports different recognizer properties for each target(Eo).

Fix build warning.

Remove Conflict

Code clean up.

Update code to supprt c# binding.

@cedric Thanks for giving opinion.

@Jaehyun_Cho Sorry im late.

Code clean up.

D8600