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?

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.

Update code

Update code

Add initialization code.

It is an eo function. why is it necessary to check null for obj?

update commit message

Update patch

• add shareable parameter

Please ignore my comment. I will update this patch as soon as possible.

I think it may be difficult to find or delete the vfd with vp applied as different vfd objects are added to the same key at vg_cache->vfd_hash.

Yes Thanks :)

@bu5hm4n No not used.

When building with json vg loader enabled, a build error occurred.

/usr/bin/ld: src/tests/evas/6440e44@@evas_suite@exe/.._.._static_libs_vg_common_vg_common_json.c.o: undefined reference to symbol 'lottie_animation_property_override'
/usr/local/lib/x86_64-linux-gnu/librlottie.so.0: error adding symbols: DSO missing from command line

Update code

Update code

already fixed

update comment

Update code

Change enum name Change_flag to flags.

LGTM :)

remove empty space

reuse boundary info

update code

Update code
Refers to the object's viewbox.

Update code

• If boundary size is 0, don't merge.
• VG obj's boundary is calculated only when pd->changed is ture.

HI :) I did a little check to solve this.
I understand why you should replace void * with array <> or iterator <>....
However, efl_gfx_path uses the data transmitted as parameters from user side and does not manage path memory separately.
If this is changed, the user who has used the existing API or the legacy API must create and pass the array type data. or legacy path apis manage to array memory.
I think, we are not ready for that yet. The path is used in many places.

I agree. thanks

update comments

I updated code. thanks

update test results

Update code - use efl_finalized_get

I removed speed comparison. There are some improvements, but almost the same speed.

Update code - use efl_finalized_get

rebase patch

I removed speed comparison. There are some improvements, but almost the same speed.

test result update

update code - use efl_finalized_get

Update code - use efl_finalized_get

update code

update code

update_code

Fix typo

Thank you for review. Update code.

Update code

@singh.amitesh ok. I got it. Thanks for comment

The code before modification refers to the location information of the object to be searched. However, the modified code does not consider the location information. This can make to compatibility issues.

remove space

Update patch.

• Add checking for composition buffer.

I think this is appropriate.

DBG->WRN