currently shadows use a property called shadow_width however css uses blur_radius
there is not only a difference in name but also in content.
from my limited testing:
shadow_width is approx (2*blur_radius)+1.
i.e.
(shadow_width-1)/2 approx blur_radius.
I am not sure what the reason for this difference in api is but it leads to unneccesary conversion efforts when given css definitions by a UI graphics designer.
I suggest renaming shadow_width to blur_radius or shadow_blur_radius and aligning values with css.
pro: better workflow, no conversions
con: we lose some resolution in the setting (which css didnt have to begin with tho)
I am aware “you can make all you want”
but shadow_spread and shadow_opacity have specific analogs in CSS that work the same as LVGL as far as i’m aware,
the analog of shadow_width in css is blur_radius though, so if you claim to implement CSS i dont understand why not to use the actual CSS definition.
This would lead to very minor code changes in lv_draw_sw_rect.c so i think this is worth changing to be more in line with CSS.
As this is a minor change and i could make a pull request for it if that would help.
would still like to get a comment on this since it it doesnt conform to the CSS definition of shadows.
see: https://www.css3.info/preview/box-shadow/
a workaround is not a good permanent solution