things specific to the canvas (evas) but not widgets or rendering
Thu, Oct 10
- Current rotate's cx and cy is double value relative to the pivot object. (e.g. 0.0 ~ 1.0, center is 0.5) So I am not sure if Vector is the correct type for this relative values although value type is the same.
I think Vector2D sounds like the type we want to have for that. Maybe its just me, but i am prefering to have a simple container over two values for the same semantical thing.
Like you said, it may be related to preference. The reason why I am not sure about this is because these parameters have similar values of the parameters of hint_align of efl_gfx_hint.eo.
BTW, I don't have any preference about this case.
I think Vector2D is the correct thing here, my idea would be that the parameters would be in the end (from : Vector2D, to : Vector2D, pivot : Efl.Canvas.Object, c : Vector2D)
Oh, I misunderstood. Now I see. So it is the same as the preference of using Vector2D type.
Mhm, after reading it a second time, i think i am a bit confused here. What is autodel deleting, the animated object, or the player ?
If auto_del is true, then player is deleted when animation ends.
I am actaully a little bit concerend about the amount of objects required something easy as a animation.... esp. with the autodel thing, so you create 2 objects just to delete them. If we publish that like this. Then we have no good way to refactor that later on ... :(
I totally agree with you that we need to reduce the number of objects which are created for easy animation.
I'm sorry I don't understand what you mean about autodel in the later comment. Could you explain please?
Mon, Oct 7
@bu5hm4n Thank you for the description :) I replied as follows.
Wed, Oct 2
@Jaehyun_Cho what do you think about those things ?
Mon, Sep 30
Aug 9 2019
Jun 3 2019
May 29 2019
Apr 23 2019
Nope, this comment was wrong and this is a regression.
Apr 10 2019
Mar 22 2019
Mar 17 2019
Described usage does not error anymore.
Mar 4 2019
Feb 14 2019
Jan 14 2019
Can anyone confirm that this is still happening ?? I ran some tests here today with some printfs added, and I am not seeing any odd damage rectangles from evas_clip.c anymore...
Jan 13 2019
oh = i didnt even know about this ticket. i was fixing error logs i found from running enlightenment so i could have some more peace and quiet... :) i'll flag this.
Since commit afb779bda5d2cea7afd1df553913ecbe2b94541f there are no more error messages form the demo program
and Elementary_test anymore. For the Terminology test case there is only one message left: