User Details
- User Since
- Mar 18 2016, 4:39 AM (327 w, 2 d)
- Availability
- Available
Feb 9 2022
Jan 27 2022
Jan 12 2022
fix typo
remove unnecessary code
Jan 10 2022
Jan 9 2022
Jun 17 2021
rebase
fix typo
May 24 2021
Hi you are right. haha..
This change has already been fixed in D12279 So I'll abandon this.
May 23 2021
Mar 18 2021
Mar 17 2021
Feb 3 2021
Jan 31 2021
Jan 28 2021
@devilhorns Hi. Maybe.. you are right. Not changed, No need to render. I think so too. When the _efl_canvas_vg_object_render function starts, if pd->changed is false, it seems that render can be skipped. But I'm not sure if I can apply that code right now...
Jan 27 2021
update code
I update a patch. thanks
Recover check "changed"
Dec 15 2020
Dec 14 2020
Dec 1 2020
It's my fault. My repo was not latest.
Thank you for check.
Nov 23 2020
I have a question. In the case of _transit_effect_rotation_op, is anti_alias not necessary?
Nov 18 2020
Nov 16 2020
This can avoid unnecessary calculations, but it does not affect what is actually represented. Therefore, it should be abandon.
fix code
Oct 30 2020
Oct 13 2020
modify code
Oct 11 2020
Sep 21 2020
Sep 14 2020
Sep 10 2020
@Hermet I have updated the patch. Please review again.
Update commit comment
Patch update
- It doesn't traverse every frame. In render_pre, check the container's alpha and set flag to sync_render of VG object's data.
Sep 9 2020
Sep 3 2020
Update comment
Update patch
Sep 2 2020
Aug 5 2020
Ok I understand this. Thank you for review :)
Looks good to me thanks
Aug 4 2020
If there is no target (info's next or prev), elm_access finds the target once again in the focus_relation (539 line).
(I think previous diff is right.)
@kimcinoo Please check this change.
I think, If evas_cache_image_data for im2 is fail, you should be returned function before freeing "im" and dropping the image.
Looks good to me
I agree
Looks good to me
Please check comment
@kimcinoo You are right. Thanks :) I updated patch.
Update patch
Please check comment
Please check comment
replaced by eina_streq. thank you for reivew
Jul 29 2020
rebase patch
(This patch is for testing. don't merge)
Jul 16 2020
Jun 24 2020
Jun 22 2020
Jun 17 2020
Please check my comment.
In my opinion, if Efl.Ui.Image needs to do the same, I think I can handle this on line 939. Is it only necessary to support legacy?
Jun 15 2020
Abandon this patch.
The way to include stroke width in container's path bounds is wrong.
We need an API of separate VG classes that can provide this feature(actual size with stroke width area), not a local function of VG Object.