Apr 5 2021
Different Platforms using this kind of progress bar and with different styles Like Horizontal progress bar, Vertical Progressbar in determinate and indeterminate mode.
Image Example: https://itinsidenews.com/uploads/gallery/202104/img_temp_606b7e8650b6e0-38134862-49373283.gif
Oct 8 2020
Aug 1 2020
Jun 1 2020
May 30 2020
May 25 2020
Hi, thank you for coming back to this.
As a general note:
May 20 2020
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.
Apr 30 2020
We already have this as eina_error_get(). It just isn't implemented or used widely.
At some point yes.
Sorry , It looks I did not know about this issue
Apr 20 2020
@l.oleksak is this ticket resolved with the commit that has gone in or is there more work needed?
will have a look.
will have a look.
Apr 18 2020
This should be fixed in 1afb26428899cf24da45b73540f711ee27679fdb
Apr 14 2020
Apr 7 2020
Apr 6 2020
Apr 1 2020
Mar 23 2020
Mono removed __MonoCS macro in version 5.0
Mar 17 2020
Mar 9 2020
Feb 21 2020
Feb 20 2020
Add a test-case.
Feb 19 2020
An item I missed: there's a value zoom_step as part of the zoom recognizer which reports zooms as multiples of a provided step value. This currently has no way to be set, but it seems like something we should have a config value for at some point, which throws us back into the efl.config disaster.